Closed mohamed-rafraf closed 3 weeks ago
Hi @mohamed-rafraf. Thanks for your PR.
I'm waiting for a gardener 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.
@mohamed-rafraf Label kind/todo does not exist.
@mohamed-rafraf Thank you for your contribution.
Thank you @mohamed-rafraf for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.
@mohamed-rafraf Label kind/todo does not exist.
/test
@DockToFuture: The /test
command needs one or more targets.
The following commands are available to trigger required jobs:
/test pull-extension-networking-calico
/test pull-extension-networking-calico-e2e-kind
/test pull-gardener-extension-networking-calico-check-renovate-config
Use /test all
to run the following jobs that were automatically triggered:
pull-extension-networking-calico
pull-extension-networking-calico-e2e-kind
/test all
/lgtm
How to categorize this PR?
This PR introduces a boolean check to determine if the cluster is dual-stack. This check prevents misconfiguration when the user specifies an
ipam.cidr
value. Ifipam.cidr
is set , it will lead to an erroneous Calico configuration for dual-stack clusters.Example configuration:
In this setup, specifying
ipam.cidr
can result in the Calico configuration containing incorrectranges
andsubnet
fields (an invalid configuration for dual-stack networks)./area networking /kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes: Fixes #
Special notes for your reviewer:
Release note: