Skip to content

ER - enable setting spec.automountServiceAccountToken to 'false' for Weblogic Server PODs controlled by WKO Operator #5345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Michalski-Piotr opened this issue Apr 2, 2025 · 2 comments

Comments

@Michalski-Piotr
Copy link

Hello,

One of our customer has requirement to set spec.automountServiceAccountToken to false for Weblogic Server PODs running in Kubernetes architecture (and controlled by Weblogic Operator).

This is driven by the security scan report:

**AVD-KSV-0036**
 
* AVD-KSV-0036 (MEDIUM): Container of Pod 'osb-domain-adminserver' should set 'spec.automountServiceAccountToken' to false
* AVD-KSV-0036 (MEDIUM): Container of Pod 'osb-domain-osb-server1' should set 'spec.automountServiceAccountToken' to false
* AVD-KSV-0036 (MEDIUM): Container of Pod 'osb-domain-osb-server2' should set 'spec.automountServiceAccountToken' to false

Based on analysis there is no automountServiceAccountToken field exposed as configurable based on Weblogic Kubernetes Operator domain.yaml configuration reference.

Reference: https://github.com/oracle/weblogic-kubernetes-operator/blob/release/4.2/documentation/domains/Domain.md

As Enhancement Request we would like to propose option to enable customers to configure this option for Weblogic Server pods.

Topic was discussed internally with Oracle Weblogic Kubernetes Operator Product Management Team and we have agreed to raise the Enhancement Request in GitHub.

Kind regards,
Piotr Michalski
Oracle CSS

@Michalski-Piotr
Copy link
Author

Customer is using currently Weblogic Kubernetes Operator 4.2.9 and below versions:

Image

@rjeberhard
Copy link
Member

This has been implemented in the branches for 4.3.0 and 4.2.17 and will be available once one of these versions is released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants