farmotive / kex Goto Github PK

flag -n would be nice if allowed to set the namespace

Is it ever really valuable to exec into the very first container listed in your namespace? Currently you have a 1/N chance with kex. Otherwise, you again type kex -n <NUM> [OPTIONS]. What if we instead make kex default to --list, and prompt for a number (it can still default to 1 if you hit enter with no number). Worst case you type one extra key… normal case, you save 8 keys (plus any addtl options). Thoughts?

Will have to sense if this alias is present and omit...

There's nothing to see:

The brew install works for Linux. So, "For macOS:" can read "Using brew"....

kex -ls:

     1 boiling-cow-rabbitmq-2375060383-xk4c6
     2	nginx-deployment-2122188915-7xrll
     3	nginx-deployment-2122188915-8rfq5
     4	nginx-deployment-2122188915-dgpzh
     5	sqe-wiremock-8xpl6
     6	tiller-deploy-553736225-s18vh
     7	warped-clam-jenkins-501160700-2cr2h

kex
error: unable to upgrade connection: container not found ("boiling-cow-rabbitmq")

Tests file should include:

• A connected cluster
• A function for minimal Deployment creation (labeled for easy cleanup)
• Test functions for all known use cases (different containers requiring different entry commands, in multiple pods, across multiple namespaces)
• A cleanup function

When using kex, if a namespace is empty, it can still be accepted as an option, which then fails when the default pod is not found. Testing for this would require querying all namespaces for pods before listing, which may be too much of a burden for the edge case.