Skip to content

Splunk Operator: Document and add support via helm for operator to use proxy #1478

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

Open
araman-m opened this issue Mar 28, 2025 · 1 comment
Assignees
Labels

Comments

@araman-m
Copy link

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 }}

@patrykw-splunk
Copy link
Collaborator

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

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

No branches or pull requests

4 participants