-
Notifications
You must be signed in to change notification settings - Fork 369
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
Rename API group "networking" to "controlplane" #1147
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -132,6 +132,12 @@ func run(o *Options) error { | |
if err != nil { | ||
return fmt.Errorf("error creating API server: %v", err) | ||
} | ||
|
||
err = apiserver.CleanupDeprecatedAPIServices(aggregatorClient) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I didn't think of it too much but does the order matter here? should we remove deprecated APIServices before installing the new ones? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Installation happens locally on controller, and new APIServices are already registered when applying the YAML. Before apiserver starts, K8s knows nothing about the new API groups. So, I think it does not matter. |
||
if err != nil { | ||
return fmt.Errorf("failed to clean up the deprecated APIServices: %v", err) | ||
} | ||
|
||
// Set up signal capture: the first SIGTERM / SIGINT signal is handled gracefully and will | ||
// cause the stopCh channel to be closed; if another signal is received before the program | ||
// exits, we will force exit. | ||
|
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.
Thanks for adding the comment!
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.
do we have a timeline in terms of releases for how long we plan to attempt deleting old apiservices? ie after X releases we will no longer clean up..