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
docs: Deprecate cluster-pool-v2beta
#25767
docs: Deprecate cluster-pool-v2beta
#25767
Conversation
/test Job 'Cilium-PR-K8s-1.25-kernel-4.19' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.25-kernel-4.19/255/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
CI failure looks like #25785 |
/test-1.25-4.19 |
CI was green. Unfortunately this needs a rebase now. |
The `cluster-pool-v2beta` IPAM mode has been added in Cilium v1.12 as a preview feature. Since then, we have added a more flexible `multi-pool` IPAM mode, which addresses some of the shortcomings of `cluster-pool-v2`. Mainly, `multi-pool` supports multiple pod CIDR pools, it has a simpler CIDR release mechanism, and it allows users to specify what IP pool a certain pod should allocate from via pod annotation. Therefore, since `cluster-pool-v2beta` was never made generally available and was never recommended for production (and indeed still has a few known limitations and bugs), we therefore deprecate it in v1.14, with the plan to remove it in v1.15. The only `cluster-pool-v2beta` feature that is lacking in `multi-pool` IPAM mode is BGP support. We intend to add BGP support to multi-pool IPAM in Cilium v1.15. This commit also hides a few mentions of the `cluster-pool-v2beta` mode from the command-line help page. This does not impact any functional behavior. Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
67e67ad
to
6f2fe9e
Compare
/test Job 'Cilium-PR-K8s-1.16-kernel-4.19' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-kernel-4.19/461/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
/test-1.16-4.19 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small change, otherwise LGTM for docs. Approving with the understanding that changes are required prior to merge.
The functionality to dynamically allocate Pod CIDRs is now provided by the | ||
more flexible ``multi-pool`` IPAM mode. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edits for clarity
The functionality to dynamically allocate Pod CIDRs is now provided by the | |
more flexible ``multi-pool`` IPAM mode. | |
Dynamic allocation of Pod CIDRs is now provided by the | |
more flexible ``multi-pool`` IPAM mode. |
The
cluster-pool-v2beta
IPAM mode has been added in Cilium v1.12 as a preview feature. Since then, we have added a more flexiblemulti-pool
IPAM mode (c.f. #22762), which addresses some of the shortcomings ofcluster-pool-v2
. Mainly,multi-pool
supports multiple pod CIDR pools, it has a simpler CIDR release mechanism, and it allows users to specify what IP pool a certain pod should allocate from via pod annotation.Therefore, since
cluster-pool-v2beta
was never made generally available and was never recommended for production (and indeed still has a few known limitations and bugs that make it unlikely it has been deployed in production), we therefore deprecate it in v1.14, with the plan to remove it in v1.15.The only
cluster-pool-v2beta
feature that is lacking inmulti-pool
IPAM mode is BGP support. We intend to add BGP support to multi-pool IPAM in Cilium v1.15.This PR also hides a few mentions of the
cluster-pool-v2beta
mode from the command-line help page. This does not impact any functional behavior.