-
Notifications
You must be signed in to change notification settings - Fork 123
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
Remove unecessary flags in cloud-controller-manager #34
Comments
@andrewsykim I'd be happy to take over this one, either partially or completely. Given the number of flags available, I'd appreciate any advice on how to determine which flags should stay and which may be dropped. Thanks! |
@timoreimann do you have all the flags handy from the DO CCM? If you list them here I can list which ones are still needed today. |
@andrewsykim sure, here you go (note that the description of the
|
Hey @andrewsykim 👋 -- have you had a chance to take a look at the output I pasted above? |
Hey @timoreimann sorry for the delay. So after going through some of the flags I actually do think we need most of those. The two that I think are safe to remove are:
@cheftako do you see anything else here that can be cleaned up? |
@andrewsykim thanks for checking. I had a few others in mind that I probably just lack context around. Could I ask you to briefly describe why these are needed:
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/lifecycle frozen |
@timoreimann are you able to work on this still? |
@andrewsykim yep for sure. It's been awhile since I checked in on this one, last time I did there were a number of open questions around some flags at #34 (comment). If you have a moment, could you go through them and let me know which of the flags I explicitly mentioned are needed for sure? |
Update embargo doc link in SECURITY_CONTACTS and change PST to PSC
There's a bunch of unnecessary flags that were added to the cloud-controller-manager as it was back ported from the kube-controller-manager. We should remove (or deprecate) those flags, specifically flags associated with a single provider (e.g. --cloud-provider-gce-lb-src-cidrs)
cc @timoreimann
The text was updated successfully, but these errors were encountered: