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

Migrate registry-operator to kubebuilder v3 #826

Closed
kim-tsao opened this issue Apr 14, 2022 · 0 comments · Fixed by devfile/registry-operator#22
Closed

Migrate registry-operator to kubebuilder v3 #826

kim-tsao opened this issue Apr 14, 2022 · 0 comments · Fixed by devfile/registry-operator#22
Assignees
Labels
area/registry Devfile registry for stacks and infrastructure

Comments

@kim-tsao
Copy link
Contributor

Which area/kind this issue is related to?

/area registry

Issue Description

The registry operator was originally built using the v2 plugin which causes problems when trying to scaffold new CRs because the artifacts wind up with a deprecated v1beta1 version. Manually updating these versions to v1 may result in unstable code especially since we will be introducing validating webhooks and a cert manager for our new CRs. To avoid any problems, we should fully migrate the operator and make it compatible with the latest controller tools/runtime.
https://book.kubebuilder.io/migration/v2vsv3.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant