Description
Is your feature request related to a problem? Please describe.
When the config.oidc.enabled
flag is set to false
, theenv
field is not generated in the Deployment manifest. This results in an invalid Kubernetes manifest and deployment failure because the env
block is expected by default.
Describe the solution you'd like
Ensure that the env
block is conditionally included or properly handled when config.oidc.enabled
is false. The Helm template should generate valid manifests in both scenarios, whether the flag is enabled or not.
Describe alternatives you've considered
One possible alternative is to include a default, empty env
field when config.oidc.enabled
is false. Another option is to restructure the Helm template to avoid generating incomplete env fields.
Additional context
his issue affects deployments where OIDC is not enabled but the manifest generation still expects an env
block.
Metadata
Assignees
Labels
Type
Projects
Status
Done
Activity