Move to k8s.io/cli-runtime about krew

[ahmetb]

No prow here, also can't assign without adding you to org or transferring repo. 🤷‍♂️

[ahmetb]

Makes sense. We don't connect to API so we don't need the restclient.

The only part that could've been useful is --output flag for kubectl krew list, and even in that case it would be severity/P2. We'll hold off on this.

[juanvallejo]

/assign

[ahmetb]

What would we get out of cli-runtime if we migrated today (other than standardized flags)?

[juanvallejo]

What would we get out of cli-runtime if we migrated today (other than standardized flags)?

Mainly those. Which we could then use to obtain a "restclient config" we could then use to talk to the kube api using k8s.io/client-go. We'd get printing and other cli helpers as well. Not really sure to what extent Krew needs all of these today though.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[ahmetb]

/close
For now krew doesn't need any of the packages offered by cli-runtime.

[k8s-ci-robot]

@ahmetb: Closing this issue.

In response to this:

/close
For now krew doesn't need any of the packages offered by cli-runtime.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.