Skip to content

Optimize olmv1 kubectl plugin UX #1851

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

Open
ankitathomas opened this issue Mar 6, 2025 · 2 comments
Open

Optimize olmv1 kubectl plugin UX #1851

ankitathomas opened this issue Mar 6, 2025 · 2 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

rework the olmv1 kubectl plugin UX from the olmv0 kubectl-operator style UX to be more consistent with olmv1 vocabulary and typical kubectl/cli best practices.

This includes updating documentation to reflect the cli structure and any changes to it.

@azych
Copy link
Contributor

azych commented Mar 10, 2025

@azych
Copy link
Contributor

azych commented Mar 10, 2025

also, some context for the ideas driving olmv1 commands up to this point: operator-framework/kubectl-operator#225 (comment) (see general comments section)

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

2 participants