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
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: