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

Add possibility to install components in hostNetwork #707

Open
v0lumehi opened this issue Jan 13, 2025 · 1 comment
Open

Add possibility to install components in hostNetwork #707

v0lumehi opened this issue Jan 13, 2025 · 1 comment

Comments

@v0lumehi
Copy link

Hi, we use our own CNI (Cilium) and therefore have to install all components in the hostNetwork. Kubernetes offers the option to do this: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#podspec-v1-core
We also had to set dnsPolicy to ClusterFirstWithHostNet in our setup.
Can we make both parameters configurable in the Helm chart?
We are currently using helm post-renderer to add the functionality and could remove it again when the helm chart offers the functionality

Image I'm using:
latest

Issue or Feature Request:
Feature Request

@ytsssun
Copy link
Contributor

ytsssun commented Jan 17, 2025

Hi @v0lumehi , thanks for cutting us this issue. To clarify, do you need this dnsPolicy overwrite to be available to all existing components? Namely:

  • brupop-agent (DaemonSet)
  • brupop-apiserver (Deployment)
  • brupop-controller-deployment (Deployment)

To approach this, we can add a top level override in the Values.yaml that apply this to all components. We can also add dedicated override at component level.

We recently merged a change to enable top level override for PodLabels (#617), we can certainly do something similar here for dnsPolicy.

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

No branches or pull requests

2 participants