Skip to content

Support for injecting custom environment in the Helm Chart #4745

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.

Sign up for GitHub

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

Merged
matthchr merged 2 commits into from
Jun 10, 2025
Merged

Support for injecting custom environment in the Helm Chart #4745

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b5ef981
Add extraEnv to the helm chart
May 23, 2025
efa0fd8
update comment
barucijah May 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions ...ervice-operator/templates/apps_v1_deployment_azureserviceoperator-controller-manager.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,6 +199,9 @@ spec:
valueFrom:
fieldRef:
fieldPath: metadata.namespace
{{- with .Values.extraEnv }}
{{- toYaml . | nindent 8 }}
{{- end }}
image: {{.Values.image.repository}}
imagePullPolicy: Always
livenessProbe:
Expand Down
9 changes: 9 additions & 0 deletions v2/charts/azure-service-operator/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -280,3 +280,12 @@ serviceAccount:
# If not set and create is true, `azureserviceoperator-default` would be used as a name
name: ""
annotations: {}

# List of extra environment variables to inject into the manager container
# Example:
# extraEnv:
# - name: ENV
# value: "prod"
# - name: SERVICE
# value: "azure-service-operator"
extraEnv: []
Loading