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
fix: use proper helm param name for specifying pod cidr #27141
Conversation
Commit 874533f93b42b071f619bd34446b110dff3fd1b2 does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
874533f
to
582b91a
Compare
Commit 874533f93b42b071f619bd34446b110dff3fd1b2 does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
Signed-off-by: Renat Tuktarov <yandzeek@gmail.com>
582b91a
to
8c0c325
Compare
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.
Nice catch! Thank you! One small nit that I have for you is the commit message, which could be a bit more specific. Something like:
docs: remove `clusterPoolIPv4PodCIDR option in k3s install
The option `clusterPoolIPv4PodCIDR option was deprecated in
Cilium 1.11 and removed from helm values in commit 1eef5ac.
This commit replaces an outdated reference to this option in
the k3s installation docs with the preferred option
`clusterPoolIPv4PodCIDRList`
Introduced in d3f2bcb ("Doc: Update k3s cilium installation to match k3s default podCIDR") which is in 1.14, I'm marking for backports for that release. |
/test |
No description provided.