-
Notifications
You must be signed in to change notification settings - Fork 575
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
Can we support ubuntu 22.04? #4050
Comments
Thanks for raising this issue. It could be a potential candidate for our roadmap. /triage accepted |
This issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Ubuntu 24.04 definitely works, see for example the documentation and AMI updates in #5133 /close |
@AndiDog: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Only kernel 5.10+ support cilumn ebbf feature. We'd like to use ebpf to replace kube-proxy.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
https://docs.cilium.io/en/v1.10/gettingstarted/kubeproxy-free/
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: