Ahmet Alp Balkan

:robot: _Beep beep! I’m a robot speaking on behalf of @ahmetb._ :robot: ----- This pull request **does not** seem to be a straightforward version bump. I'll have a human review...

:robot: _Beep beep! I’m a robot speaking on behalf of @ahmetb._ :robot: ----- This pull request **does not** seem to be a straightforward version bump. I'll have a human review...

:robot: _Beep beep! I’m a robot speaking on behalf of @ahmetb._ :robot: ----- Thanks for submitting your kubectl plugin to Krew! One of the krew-index maintainers will review it soon....

/lgtm /approve Thanks! Also, please consider setting up [Krew release automation](https://krew.sigs.k8s.io/docs/developer-guide/release/automating-updates/) which helps you skip manually making updates to your Krew manifests on each new version and send a pull...

Why not just use your shell history (Ctrl+R) like you would for any other command, like "cd" or "git checkout"? Or are you only proposing we change the ordering that...

Does kubectl actually work? At any rate the error is basically saying the kubeconfig file you have is misconfigured. Maybe use absolute paths?

Can you attach the "kubectl get ns -v7" output please? Also what version of apiserver is this cluster running. Assuming k3s doesn't distribute its own kubectl, this should be working.

:robot: _Beep beep! I’m a robot speaking on behalf of @ahmetb._ :robot: ----- This pull request **does not** seem to be a straightforward version bump. I'll have a human review...

:robot: _Beep beep! I’m a robot speaking on behalf of @ahmetb._ :robot: ----- This pull request **does not** seem to be a straightforward version bump. I'll have a human review...

:robot: _Beep beep! I’m a robot speaking on behalf of @ahmetb._ :robot: ----- This pull request **does not** seem to be a straightforward version bump. I'll have a human review...