Telemaco019

4 ms·

1.
Kubesafe now shows how often it saved you from targeting the wrong cluster(github.com)
1 points by Telemaco019 11mo ago|0 comments
2.
Sqlalchemy-tenants: Because "oops, forgot WHERE tenant= " is not fun(github.com)
3 points by Telemaco019 1y ago|0 comments
3.
Show HN: Sqlalchemy-tenants – Because "oops, forgot WHERE tenant= " is not fun(github.com)
1 points by Telemaco019 1y ago|0 comments
4.
by Telemaco019 2y ago
Absolutely! kubesafe is simply a wrapper, so you can use it with any Kubernetes tool by passing the tool as the first argument to kubesafe. Example with kubecolor: `kubesafe kubecolor get pods --all-namespaces`
5.
by Telemaco019 2y ago
I think it’s a tradeoff between safety and speed. Having only the CI/CD with production access can significantly slow you down, especially in the early stages when you’re focused on the product and still building out your tooling/
6.
by Telemaco019 2y ago
Cool project, I didn't know it. I love the idea, thanks for sharing it!
7.
by Telemaco019 2y ago
I also have it in my zsh config, but that didn’t stop me from screwing up in the past. Having an active confirmation prompt for potentially risky commands is what works best for me
8.
by Telemaco019 2y ago
Got burned too, we've all been there I guess :) I also tried to avoid current context initially, but it just slowed me down. Switching between clusters is so much easier with the current context and kubectx. That’s why I built kubesafe
9.
by Telemaco019 2y ago
You're welcome! And thanks again for the feedback!
10.
by Telemaco019 2y ago
Thanks Robert! Yes, you can achieve this with ACLs in Kubernetes, but it requires setting up multiple Roles and contexts. Even then, you might accidentally switch to a higher-permission Role and accidentally run a risky command, thinking yo
11.
by Telemaco019 2y ago
Thanks for the feedback John! You're right, that's pretty much it :) I developed kubesafe because (1) I was tired of tinkering with shell aliases and scripts (especially when I wanted to define protected commands) and (2) I needed
12.
Kubesafe: Never run Kubernetes commands on the wrong cluster again(github.com)
73 points by Telemaco019 2y ago|48 comments
13.
Launching kubesafe: Your safety net for managing multiple Kubernetes clusters(github.com)
2 points by Telemaco019 2y ago|0 comments
14.
Duplik8s: New kubectl plugin to duplicate Kubernetes resources(github.com)
2 points by Telemaco019 2y ago|0 comments
15.
Show HN: Nos – Open-Source to Maximize GPU Utilization in Kubernetes(github.com)
2 points by Telemaco019 4y ago|0 comments