IPv6 default route #7314
IPv6 default route #7314
Conversation
|
This allows to create IPv6 clusters with KIND |
aojea
force-pushed
the
ipv6_default_gw
branch
3 times, most recently
from
eb75757
to
66cc1e2
Compare
|
@mheon PTAL, I've removed the dependencies, kept the same signature for |
podman containers using IPv6 were missing the default route, breaking deployments trying to use them. The problem is that the default route was hardcoded to IPv4, this takes into consideration the podman subnet IP family to generate the corresponding default route. Signed-off-by: Antonio Ojea <aojea@redhat.com>
|
/retest |
|
@aojea: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
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/test-infra repository. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, mheon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
/lgtm |
github-actions
bot
added
the
locked - please file new issue/PR
The networking configuration was assuming always that the default
gateway was 0.0.0.0/0, that does not work if we have IPv6
containers.
We must generate the corresponding default route depending of the
IP family of the subnet used.
Signed-off-by: Antonio Ojea aojea@redhat.com