-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[Digital Ocean] Use Debian10 as default image #10098
Conversation
Hi @srikiz. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
/ok-to-test |
Especially since citing cilium as the reason, I would go for Ubuntu. Debian uses nftables by default and cilium doesn't support that. Users need various workarounds for switching to iptables legacy to avoid having both legacy and nftables rules at play. |
Co-authored-by: Ciprian Hacman <[email protected]>
Thanks @srikiz. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman, srikiz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…-upstream-release-1.19 Automated cherry pick of #10098: Use Debian10 image for DO
Thanks @hakman for cherry-picking this into release-1.19 ! |
😉 |
Cilium leverages and builds on the kernel BPF functionality as well as various subsystems which integrate with BPF. Therefore, host systems are required to run Linux kernel version 4.9.17 or later to run a Cilium agent.
Using Debian10 should ensure we have the latest kernel that Cilium expects.