Skip to content
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 for development purposes #1083

Closed
wants to merge 1 commit into from

Conversation

Danil-Grigorev
Copy link
Contributor

What this PR does / why we need it:

Fixes #1082

  • squashed commits into logical changes
  • includes documentation
  • adds unit tests
  • adds or updates e2e tests

@Danil-Grigorev Danil-Grigorev requested a review from a team as a code owner February 17, 2025 14:08
@Danil-Grigorev Danil-Grigorev changed the title Enable CAPI UI extension installation ✨ Enable CAPI UI extension installation Feb 17, 2025
@Danil-Grigorev Danil-Grigorev force-pushed the auto-install-ui branch 3 times, most recently from 28ead87 to d463f94 Compare February 17, 2025 15:00
anmazzotti
anmazzotti previously approved these changes Feb 17, 2025
yiannistri
yiannistri previously approved these changes Feb 18, 2025
Copy link
Contributor

@yiannistri yiannistri left a 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.

@Danil-Grigorev Danil-Grigorev dismissed stale reviews from yiannistri and anmazzotti via eaf8ab2 February 18, 2025 15:18
anmazzotti
anmazzotti previously approved these changes Feb 18, 2025
// 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{
Copy link
Member

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It can be, but this controller does not set any spec fields, only moves the UI plugin to the cattle-ui-system-namespace, once this namespace is created. It may also be used later to not move and simply delete UIPlugin if it interferes with existing one in the namespace already. Helm has problems with cleaning up or replacing resources if they weren’t created by it, so a controller is better suited to accommodate this custom logic.

@Danil-Grigorev Danil-Grigorev force-pushed the auto-install-ui branch 2 times, most recently from 253dea1 to 2963f1d Compare February 19, 2025 16:47
anmazzotti
anmazzotti previously approved these changes Feb 20, 2025
Signed-off-by: Danil-Grigorev <danil.grigorev@suse.com>
@Danil-Grigorev
Copy link
Contributor Author

I think we need to postpone this addition until we have a clear installation path supported by the org. I’ll close it for now.

@Danil-Grigorev Danil-Grigorev changed the title ✨ Enable CAPI UI extension installation ✨ Enable CAPI UI extension installation for development purposes Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Seamless Turtles UI development installation with Turtles chart
4 participants