-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Deprecate IP Family builtin variable #10554
🌱 Deprecate IP Family builtin variable #10554
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+ regen
Thx! /lgtm |
LGTM label has been added. Git tree hash: 177766d2dfe6ea40207cf3e4cb41dc4dbe4660fd
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
Maybe we should close #7521 and just have one umbrella issue to remove all deprecated types with the next apiVersion (we can link to the corresponding deprecation issues) Just to make it easier to keep an overview over all deprecations |
What this PR does / why we need it:
IPFamily is not a concept in Kubernetes. It was originally introduced in CAPI for CAPD.
This PR kicks off the deprecation & removal process, at the end of this process IP Familiy will exist only inside CAPD as a convenience for testing.
Which issue(s) this PR fixes:
Part of #7521
/area clusterclass