-
Notifications
You must be signed in to change notification settings - Fork 22
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
✨ Enable CAPI UI extension installation #1083
base: main
Are you sure you want to change the base?
Conversation
c752c12
to
28ead87
Compare
Signed-off-by: Danil-Grigorev <[email protected]>
28ead87
to
d463f94
Compare
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 addressing this, apart from a minor typo this looks good.
Co-authored-by: Yiannis Triantafyllopoulos <[email protected]>
eaf8ab2
// SetupWithManager sets up the controller with the Manager. | ||
func (r *UIPluginReconciler) SetupWithManager(_ context.Context, mgr ctrl.Manager, _ controller.Options) error { | ||
uiPlugin := &metav1.PartialObjectMetadata{} | ||
uiPlugin.SetGroupVersionKind(schema.GroupVersionKind{ |
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.
should this be a part of the rancher API wrapper?
- variable: capi.enabled | ||
default: true | ||
type: boolean | ||
description: "Flag to enable or disable installation of CAPI UI extension. If set to false then you will need to install CAPI UI extension manually." |
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.
is it possible to add to the description that UI is still experimental? can be done in a follow-up
What this PR does / why we need it:
Fixes #1082