-
Notifications
You must be signed in to change notification settings - Fork 108
🌱 remove cluster api featuregate flags #155
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
Conversation
CAPI operator doesn't need Cluster API featuregate flags as it doesn't work with them. Seem like it was copied by mistake, so it's safe to remove it.
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.
Nice catch!
/lgtm
LGTM label has been added. Git tree hash: 492003808eb65fc3436f8549bdcbba4659f34809
|
/retest |
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.
/lgtm
It looks like there are other places where feature gates are mentioned in the repo. |
@damdo no, we need all other places. there featuregates are used to be passed to capi controller |
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.
Makes sense.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damdo 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 |
/retest |
What this PR does / why we need it:
CAPI operator doesn't need Cluster API featuregate flags as it doesn't work with them. Seem like it was copied by mistake, so it's safe to remove it.