-
Notifications
You must be signed in to change notification settings - Fork 545
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
add ipv6 support in k8s and calico config,it compatible only ipv4 provide #2142
Conversation
Change-Id: I13d12caebced1c6fb5cdbcaa1b70b5154ba701ba
Change-Id: If68f60ccc1fae9918e78a9477929f0a9ee64ab92
Change-Id: I472ed48889750c9226c4d28c7b31761c49d3265b
Change-Id: Ib52730123b41b4ab69dc29ebf9e2ca95af1da44b
Change-Id: I40af792c7437fca41472e8f5012e7f78952fbf96
Change-Id: I32736b0bb28da4434067ae262dc1b484a90c8c00
Change-Id: I66b6c33b34b7588a0181f8d031d9965afa95560c
Change-Id: I7301e6a5957fbea48b73f37cee5a617db8c5a693
Change-Id: Icf7289e0914200880819be4a3464427426585abe
Change-Id: I4f153af1dfd914eeaaf0d419a915bb913e775ba2
Change-Id: I0929936fe524803cf8b0795b56281b232f96238a
…ddress not provide Change-Id: I9388a58780e467e9c1283bf29c07102ec2ba5b54
/assign @rayzhou2017 |
@wenwenxiong Thanks for this contributions ! |
LGTM label has been added. Git tree hash: 31d65032908856595ca511274f275006075f08ce
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pixiake, wenwenxiong 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 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
add ipv6 support in k8s and calico config,it compatible only ipv4 provide
like doc/config-example.md
just change host.internalAddress, kubePodsCIDR, kubeServiceCIDR with ipv6 address and cidr, you can deploy k8s with calico support ipv4/ipv6 cluster
and it compatible only ipv4 provide
Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: