If you create port-forward on lens and eventually close lens at a later time. When you re-open lens, port-forward will stay open. I personally prefer doing it through kubectl.
Oh yeah, I wouldn't like that either. K9s is pretty good with port forwarding: there's a quick shortcut to start it and then you're easy to stop, plus it doesn't persist between k9s restarts
i used k9s for port-forwarding too, and it lacks features that tools like kubefwd or krelay have (eg udp port forward, tls and reconnections). i say this cuz i also built a tool for kubectl port-forward and sometimes it's tricky 🙃
Yep, I have develop very large harness in jsonnet and considering kcl as it has a superior feature set. My poc so far so good. Making impossible for devs to configure things incorrectly, thanks to schemas and validations. I kinda don't like that I have to use packages for local fileaystem monorepo thing, but it's manageable.
K8s is only one configuration target. I now want womething more generic to drive infra tf configuration, app configuration, Metadata configuration, all the things lol.
Yeah, I do OpenLens with the '@alebcay/openlens-node-pod-menu' extension and really like it. It's user-friendly enough to onboard newer folks and does enough for me to work with all of our clusters.
Yq, kubectl, k9s
Also shoutout my crappy little custom bash command to pull rancher kubeconfigs in my clipboard and put them into a dedicated file in .kube
Sure paying for something isn't for everyone, especially those who aren't using it in a professional setting. Me personally I use it professionally and believe the dev working on the tool deserves to be compensated. I have a team license with 3 seats for my self and 2 others on my team.
Oh, 100%. But I'm running k3s in my homelab with no enterprise budget, so I have to be frugal, haha.
Maybe something to try at work, though...although I wish there was a free homelab version that worked for more than 15 days. Have to be able to tell the boss what's so good about it! 🙃
Just because one person uses one thing, and someone else uses another doesn't make one or the other better? OP asked for favourites tools, I linked my personal favourite, it's that simple.
i mean logic tells me if one pays for a tool, the tool probably does something better than a free alternative.
if you don’t want to elaborate or just enjoy paying for things that can be had for free all the power to you.
I hate the way they sell a 40$ more expensive perpetual license that is only valid for 1 year of updates. You need to use it 8 months after you stop receiving updates to even it out.
Giving obviously bad payment options really hurts my goodwill towards a company.
K9s
Kubie for managing kubeconfigs
Also yaookctl which is specifically for YAOOK managed Kubernetes clusters but provides many different tools Iike connections to MySQL pods in Openstack
KubeZtl - https://github.com/openziti-test-kitchen/kubeztl/. It has a zero trust network overlay embedded into it so that the K8S API can be 'dark' with no inbound ports.
k9s
Classic
Yeah, k9s is dope. Use it every day!
Definitely k9s .. but also really appreciate stern for realtime filtered log streams
Is stern maintained anymore?
Latest release 3w ago: https://github.com/stern/stern/releases
ArgoCD/Flux - do they count? Lol
Yq
Facts, and JQ
I use kubectl + jq as a poor-man’s log streaming/filtering solution. Works good enough for debugging.
That’s the OG way of doing it
Get on helm.
K9s
Does kubectx count?
Maybe it’s not the same but kubectx would set the context to ALL open terminals…. I’ve used kubie since
Why isn't this just an alias..? alias kubectx="kubectl config use-context" Same with kubens
Because it also lists all the contexts and highlights the current one. Same as kubens with namespaces
Lens
OpenLens? Together with the plugin to bring back logs and terminal access 🤬
I hate lens port-forwarding
I'm not a Lens user. What does it do for port forwarding that you dislike?
If you create port-forward on lens and eventually close lens at a later time. When you re-open lens, port-forward will stay open. I personally prefer doing it through kubectl.
Oh yeah, I wouldn't like that either. K9s is pretty good with port forwarding: there's a quick shortcut to start it and then you're easy to stop, plus it doesn't persist between k9s restarts
i used k9s for port-forwarding too, and it lacks features that tools like kubefwd or krelay have (eg udp port forward, tls and reconnections). i say this cuz i also built a tool for kubectl port-forward and sometimes it's tricky 🙃
kubefwd looks interesting, thanks. I have heard of it
You can just delete them from the port-forwarding tab.
Jsonnet. A imo good alternative to yaml and helm. Atleast for internal development. Checkout bitnamis jsonnet chart for k8s resoureces
KCL. A simpler and more Python like configuration language. 🆕
Yep, I have develop very large harness in jsonnet and considering kcl as it has a superior feature set. My poc so far so good. Making impossible for devs to configure things incorrectly, thanks to schemas and validations. I kinda don't like that I have to use packages for local fileaystem monorepo thing, but it's manageable.
Jsonnet is also pretty decent if combined with https://github.com/yannh/kubeconform - we run it on each PR, and it's blazingly fast
K8s is only one configuration target. I now want womething more generic to drive infra tf configuration, app configuration, Metadata configuration, all the things lol.
Lens
kubetail / stern
Kustomize
Openlens, really sad that it doesn’t get any maintenance. :(
Yeah, I do OpenLens with the '@alebcay/openlens-node-pod-menu' extension and really like it. It's user-friendly enough to onboard newer folks and does enough for me to work with all of our clusters.
Yq, kubectl, k9s Also shoutout my crappy little custom bash command to pull rancher kubeconfigs in my clipboard and put them into a dedicated file in .kube
kubectl neat is pretty.... Should I say it... Neat
Same as last time. It's still grep
ksniff ( it's a kubectl plugin) you can forward pod traffic directly into wireshark for debugging
https://aptakube.com/
I was intrigued until I saw the monthly subscription. I'll stick with k9s. 🙃
Sure paying for something isn't for everyone, especially those who aren't using it in a professional setting. Me personally I use it professionally and believe the dev working on the tool deserves to be compensated. I have a team license with 3 seats for my self and 2 others on my team.
Oh, 100%. But I'm running k3s in my homelab with no enterprise budget, so I have to be frugal, haha. Maybe something to try at work, though...although I wish there was a free homelab version that worked for more than 15 days. Have to be able to tell the boss what's so good about it! 🙃
struggle to see how is this better than k9s
Just because one person uses one thing, and someone else uses another doesn't make one or the other better? OP asked for favourites tools, I linked my personal favourite, it's that simple.
i mean logic tells me if one pays for a tool, the tool probably does something better than a free alternative. if you don’t want to elaborate or just enjoy paying for things that can be had for free all the power to you.
I hate the way they sell a 40$ more expensive perpetual license that is only valid for 1 year of updates. You need to use it 8 months after you stop receiving updates to even it out. Giving obviously bad payment options really hurts my goodwill towards a company.
My org pays for Lens subscriptions for many of us and it does make my day significantly less painful!
K9s Kubie for managing kubeconfigs Also yaookctl which is specifically for YAOOK managed Kubernetes clusters but provides many different tools Iike connections to MySQL pods in Openstack
Ytt for yaml templating
KubeZtl - https://github.com/openziti-test-kitchen/kubeztl/. It has a zero trust network overlay embedded into it so that the K8S API can be 'dark' with no inbound ports.
Helm
kube-capacity
Dive is a good one for me i can see everything that is Happening in der Container images.
Stern and flux
https://github.com/stern/stern and https://github.com/flowerinthenight/kubepfm
`oc`
Databricks’ Click, a Kubernetes REPL
I like oc, because it's short xD
k8sgpt
What’s this?
Terraform
Terraform
go
Flux, and can i say helm?
Not the helm