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

CFP: Option to configure timeout for lease lock acquisition in cilium operator. #38144

Open
akash-gautam opened this issue Mar 12, 2025 · 1 comment
Labels
kind/cfp kind/feature This introduces new functionality.

Comments

@akash-gautam
Copy link

Cilium Feature Proposal

Is your proposed feature related to a problem?

I have a k8s cluster with a remote control plane in a region different from the worker nodes in my cloud provider. When I install Cilium, the Cilium operator can't always acquire the lease lock in the set timeout of 5s. This works sometimes but fails more often.

level=error msg="error retrieving resource lock kube-system/cilium-operator-resource-lock: Get \"https://<api-server>:30071/apis/coordination.k8s.io/v1/namespaces/kube-system/leases/cilium-operator-resource-lock?timeout=5s\": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" subsys=klog

Describe the feature you'd like

There should be an option to configure the timeout of lease acquisition in Cilium operator so that admins can increase it if the latency between the worker nodes and the control plane is higher & the operation doesn't always conclude in 5s.

(Optional) Describe your proposed solution

Introduce a flag in the cilium operator that allows configuring the timeout for acquiring the lease lock.

@akash-gautam akash-gautam added kind/cfp kind/feature This introduces new functionality. labels Mar 12, 2025
@yrsuthari
Copy link
Contributor

I would like to give it a try!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cfp kind/feature This introduces new functionality.
Projects
None yet
Development

No branches or pull requests

2 participants