Skip to content
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

[kube-prometheus-stack] support dual stack clusters #4429

Closed
M0NsTeRRR opened this issue Apr 6, 2024 · 2 comments · Fixed by #4472
Closed

[kube-prometheus-stack] support dual stack clusters #4429

M0NsTeRRR opened this issue Apr 6, 2024 · 2 comments · Fixed by #4472
Labels
enhancement New feature or request

Comments

@M0NsTeRRR
Copy link
Contributor

M0NsTeRRR commented Apr 6, 2024

Is your feature request related to a problem ?

There is no way for me to set the ipFamilyPolicy and ipFamilies to "preferDualStack" in the current helm chart for services

Describe the solution you'd like.

Add the possibility to set in the ipFamilyPolicy and ipFamilies

Describe alternatives you've considered.

Patch the current helm chart with kustomize

Additional context.

No response

@M0NsTeRRR M0NsTeRRR added the enhancement New feature or request label Apr 6, 2024
@M0NsTeRRR
Copy link
Contributor Author

M0NsTeRRR commented Apr 6, 2024

I will create the MR for this issue but I need to know if you want each services to be configurable with dual-stack or a global configuration for all services is sufficient.
I will of course reuse ipDualStack logic from other chart.

@zeritti zeritti changed the title [kube-prometheus-stack] support dual stuck clusters #2632 [kube-prometheus-stack] support dual stuck clusters Apr 6, 2024
@zeritti zeritti changed the title [kube-prometheus-stack] support dual stuck clusters [kube-prometheus-stack] support dual stack clusters Apr 6, 2024
@jkroepke
Copy link
Member

Each service should be preferred.

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

Successfully merging a pull request may close this issue.

2 participants