Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Provide Calico CNI IPv4/v6/Dual Stack Support in Airshipctl #655

Open
manojkva opened this issue Oct 17, 2021 · 2 comments
Open

Provide Calico CNI IPv4/v6/Dual Stack Support in Airshipctl #655

manojkva opened this issue Oct 17, 2021 · 2 comments
Assignees
@manojkva
Labels
enhancement New feature or request
Milestone
Future

Comments

@manojkva
Copy link
Contributor

The calico Installation CR for tigera-operator currently supports only IPv4.

Propose to move the current Issue in Treasuremap (airshipit/treasuremap#22) to airshipctl as it will provide flexibility to override the calico IPv4/v6 or Dual stack at site level.

Working demo : https://review.opendev.org/c/airship/airshipctl/+/810449
I have used AIAP with a private IPv6 network to demonstrate a dualstack setup using airship.

Hackmd : https://hackmd.io/OTWXJ0fSTTak_Zt33lilww?view
@manojkva manojkva added enhancement New feature or request triage Needs evaluation by project members labels Oct 17, 2021
@manojkva manojkva mentioned this issue Oct 17, 2021
Closed
@eak13 eak13 removed the triage Needs evaluation by project members label Oct 27, 2021
@eak13 eak13 added this to the Future milestone Oct 27, 2021
@manojkva
Copy link
Contributor Author

I have already put in effort on this (as a part of testing Dualstack for Treasuremap). You could assign this to me.

@manojkva
Copy link
Contributor Author

Working PS = https://review.opendev.org/c/airship/airshipctl/+/815652

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manojkva manojkva

Labels
enhancement New feature or request
Projects
None yet
Milestone
Future
Development

No branches or pull requests
2 participants
@manojkva @eak13