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

Move the olmv1 implementation in kubectl-operator to the operator-controller repo #1850

Open
ankitathomas opened this issue Mar 6, 2025 · 0 comments
Labels
epic/kubectl-operator-plugin v1.x Issues related to OLMv1 features that come after 1.0

Comments

@ankitathomas
Copy link
Contributor

ankitathomas commented Mar 6, 2025

Move the kubectl-operator olmv1 plugin related files to a subdirectory in the operator-controller repo including:

  • all files related to implementations
  • e2e and unit tests
  • CI, build targets etc.
  • documentation

A/C:

  • All olmv1 related files are removed from kubectl-operator, and present in the operator-controller repo
  • All related tests pass, along with CI
  • Any existing documentation is moved within the relevant operator-controller subdirectory.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic/kubectl-operator-plugin v1.x Issues related to OLMv1 features that come after 1.0
Projects
Status: No status
Development

No branches or pull requests

1 participant