Add support for Cilium Bandwidth Manager and BBR

[nuved]

This adds support for enabling Cilium's Bandwidth Manager and BBR congestion control directly from the kOps Cilium networking spec.

Two new fields are added to spec.networking.cilium:

• enableBandwidthManager – enables Cilium's eBPF-based Bandwidth Manager, which honors the kubernetes.io/egress-bandwidth Pod annotation and provides EDT-based egress rate-limiting.
• enableBBR – enables BBR (Bottleneck Bandwidth and Round-trip propagation time) as the TCP congestion control algorithm for pod traffic. Requires enableBandwidthManager and a node kernel >= 5.18. kOps also configures the node sysctls (net.core.default_qdisc=fq, net.ipv4.tcp_congestion_control=bbr).

Validation rejects enableBBR without enableBandwidthManager. The fields are plumbed through all API versions (internal, v1alpha2, v1alpha3) with regenerated conversion/deepcopy code, wired into the Cilium addon template and nodeup sysctls, and documented in docs/networking/cilium.md.

/kind feature

Added `spec.networking.cilium.enableBandwidthManager` and `spec.networking.cilium.enableBBR` to enable Cilium's Bandwidth Manager and BBR congestion control.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: nuved / name: nuved (ad71ee5)

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign hakman for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubernetes-prow]

Welcome @nuved!

It looks like this is your first PR to kubernetes/kops 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kops has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[kubernetes-prow]

Hi @nuved. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.