4 ms·
IMO uni-tools like kubectx are pointless Huge fan of fzf + bash history Trigger fzf, search “context cluster-name” done Learning a bespoke tool to run one ba
by one2manydeps 6y ago
IMO uni-tools like kubectx are pointless
Huge fan of fzf + bash history
Trigger fzf, search “context cluster-name” done
Learning a bespoke tool to run one bash command is poor craftsmanship, won’t be worth knowing about once Kube is entirely wrapped by some providers HTTP API, and this is all managed by GUI based services, obsoleting “SRE” teams at places that aren’t Google scale
The excitement of Kube will go the way Puppet and Chef have. It’s just HTTP commands putting some YAML or JSON which is metadata for how to manage cgroups
Oh right but Google and Oreilly flooded the world with books, so kiss the rings.
- pj3677 6y agoI try to be focused on the results, not the tools per se. For me, kubectx makes it easier to view and switch between context. I run "kubectx 'context-name'" and it's done :)
- one2manydeps 6y agoThe results I’m chasing are fewer uni-task tools Ctrl+r to get fzf, searching “context prod” pulls up my last use of the kubectl form of the change context command Desired results are subjective
- Cpoll 6y ago> obsoleting "SRE" teams I'm not sure this follows. Having GUI tools that do everything works great until you have a use-case outside of the scope of the tool, or something goes wrong, then you'll need to learn the inner workings of the tool anyway (if you're lucky enough to be able to access the tool behind the managed service). I've seen this with all manner of managed databases, as well as with Amazon ECS and Fargate. Not to say that you're wrong about kubectx, just that I don't agree with the logic. Edit: On an unrelated note, I just realized that I compulsively and without thinking replaced the left/right quotation marks after copying the text from your comment.