You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is currently not documented how Splunk Operator can leverage a proxy
it can be necessary for example to reach s3 bucket for app management purposes
Following discussions, the generic way to do it is via env variables env: - name: HTTP_PROXY value: "http://your-proxy-server/:port" - name: HTTPS_PROXY value: "http://your-proxy-server/:port" - name: NO_PROXY value: "localhost,127.0.0.1,.your-domain.com"
and helm could look
env:
{{- range .Values.env }}
- name: {{ .name }}
value: {{ .value | quote }}
{{- end }}
The text was updated successfully, but these errors were encountered:
Hey @araman-m, I've merged #1490. I believe this resolve your issue.
I've added list extraEnvs to splunk-operator chart. The same functionality for splunk-enterprise already exist under extraEnv name
Please select the type of request
Enhancement
Tell us more
It is currently not documented how Splunk Operator can leverage a proxy
it can be necessary for example to reach s3 bucket for app management purposes
Following discussions, the generic way to do it is via env variables
env: - name: HTTP_PROXY value: "http://your-proxy-server/:port" - name: HTTPS_PROXY value: "http://your-proxy-server/:port" - name: NO_PROXY value: "localhost,127.0.0.1,.your-domain.com"
and helm could look
env:
{{- range .Values.env }}
- name: {{ .name }}
value: {{ .value | quote }}
{{- end }}
The text was updated successfully, but these errors were encountered: