Set 'kubernetes' IPAM in kube-proxy free guide#12246
Conversation
|
Commit a73e68781a908ab761c4ff9664abcfcbbfa8e564 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 |
There was a problem hiding this comment.
Thanks for the PR, this should be --set config.ipam=kubernetes instead of --set global.ipam.operator.clusterPoolIPv4PodCIDR=10.217.0.0/16
|
@Maireo I also changed the base branch to be master because we need to fix this first in the master and after being merged we will perform the backport to 1.8. Can you sing your commit as instructed in #12246 (comment)? Thanks |
a73e687 to
543a9b0
Compare
|
Commit 543a9b08d902625e15c67f18eacde29bd1e6ce7d 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 |
|
Please set the appropriate release note label. |
|
Please set the appropriate release note label. |
5 similar comments
|
Please set the appropriate release note label. |
|
Please set the appropriate release note label. |
|
Please set the appropriate release note label. |
|
Please set the appropriate release note label. |
|
Please set the appropriate release note label. |
|
Coverage decreased (-0.2%) to 36.928% when pulling 46004cac297af02e29c78632aef68964c6f63305 on MaiReo:helm-pod-cidr-to-10-217-0-0 into 55dd1b9 on cilium:master. |
|
Commits 543a9b08d902625e15c67f18eacde29bd1e6ce7d, 5136d26feb5a2a82301f199d34043b60cfdcffb1 do 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 |
|
Commits 543a9b08d902625e15c67f18eacde29bd1e6ce7d, 5136d26feb5a2a82301f199d34043b60cfdcffb1 do 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 |
|
I forgot to set Signed-off-by when commiting. Should I to close the PR? |
@Maireo no need for that, you can squash all your commits with |
The pod cidr should match 10.217.0.0/16 mentioned previously, not the default value 10.0.0.0/16 set by default via helm in this tutorial. --set global.ipam.operator.clusterPoolIPv4PodCIDR=10.217.0.0/16 Signed-off-by: André Martins <andre@cilium.io> Signed-off-by: MaiReo <sawako.saki@gmail.com>
46004ca to
056b5ef
Compare
It's no longer required to specify podCIDR [1] when provisioning k8s with kubeadm for Cilium. Removing this allows us to simplify the guide by getting rid of passing the ipam mode to helm which was introduced by #12246. [1]: kubernetes/website#21432 (comment) Signed-off-by: Martynas Pumputis <m@lambda.lt>
It's no longer required to specify podCIDR [1] when provisioning k8s with kubeadm for Cilium. Removing this allows us to simplify the guide by getting rid of passing the ipam mode to helm which was introduced by #12246. [1]: kubernetes/website#21432 (comment) Signed-off-by: Martynas Pumputis <m@lambda.lt>
[ upstream commit d131945 ] It's no longer required to specify podCIDR [1] when provisioning k8s with kubeadm for Cilium. Removing this allows us to simplify the guide by getting rid of passing the ipam mode to helm which was introduced by #12246. [1]: kubernetes/website#21432 (comment) Signed-off-by: Martynas Pumputis <m@lambda.lt> Signed-off-by: Michal Rostecki <mrostecki@opensuse.org>
[ upstream commit d131945 ] It's no longer required to specify podCIDR [1] when provisioning k8s with kubeadm for Cilium. Removing this allows us to simplify the guide by getting rid of passing the ipam mode to helm which was introduced by #12246. [1]: kubernetes/website#21432 (comment) Signed-off-by: Martynas Pumputis <m@lambda.lt> Signed-off-by: Michal Rostecki <mrostecki@opensuse.org>
The pod cidr should match 10.217.0.0/16 mentioned previously,
not the default value 10.0.0.0/16 set by default via helm in this tutorial.
Appended '--set global.ipam.operator.clusterPoolIPv4PodCIDR=10.217.0.0/16' to the end of the helm command line.
Tested with
Kubernetes v1.17.5
cri-o v1.17
I know none about ipam, and may be blinded
Is this difference ( not match cidr assigned by kube-controller-manager) OK?