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 turn Off Cilium Socket-Level Load Balancing #490

Open
4FunAndProfit opened this issue Nov 24, 2024 · 3 comments
Open

Comments

@4FunAndProfit
Copy link

4FunAndProfit commented Nov 24, 2024

Hello !

I want to use this beautiful tool for my project!

Yet I have an issue, is it possible to add possibility to turn off Off Socket-Level Load Balancing in cilium config?

Indeed I need to use with Linkerd and this is required (https://linkerd.io/2-edge/reference/cluster-configuration/#cilium)

This behavior can be turned off in Cilium by [turning off socket-level load balancing for pods](https://docs.cilium.io/en/v1.13/network/istio/#setup-cilium) through the CLI option --config bpf-lb-sock-hostns-only=true, or through the Helm value socketLB.hostNamespaceOnly=true.

I don't see any way to add this config to cni yaml config ? (Same for cni.exclusive=false)

Thanks a lot for your help :))

@vitobotta
Copy link
Owner

Hi! Right now, the Cilium settings aren't really customizable because it's a recent addition and I haven't had the chance to make the configuration more flexible yet. But don't worry, it will be in a future release. For now, you can edit the file at https://github.com/vitobotta/hetzner-k3s/blob/main/src/kubernetes/software/cilium.cr to change the Helm chart config, and run hetzner-k3s locally using Crystal instead of the official binary. It's a bit of a workaround, but it should work for now.

@4FunAndProfit
Copy link
Author

Oh Thanks a lot @vitobotta ! 🥰

@vitobotta
Copy link
Owner

Np :)

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