Contributors are very welcome but while talking with people willing to contribute or contributing already it seems that getting started is difficult.

This task can be a good starting point for a new contributor willing to understand how the project works.

itaysk/kubectl-neat#13 added basic CI but I noticed it's building twice on a common use case: once for push and again for PR event. the fix is probably something with adding branch filtering to the triggers.

When I ran the command to set cluster status to active without passing the environment, the call returns a "Setting cluster status active" message but does not really set the cluster to active. But when I pass --environment dev I see the following output.

Setting cluster environment to dev
Setting cluster status active

Does not work(which is great): `kubectl hyperkube set-cluste

Currently, when no volumes are found the command does not display anything. So it's unclear if the command succeeded or not.

It would be better, if the command would print some informative message, similar to what kubectl get pods does:

No resources found in default namespace.

support editing multiple secrets