robusta VS kubectx

To put one more option out there, we use Hikaru (https://pypi.org/project/hikaru/) in Robusta.dev (https://github.com/robusta-dev/robusta) and have been pretty happy with it. Example code below:

  with Pod().read(name='thename', namespace='the-namespace') as p:

Open Source alternative based on Prometheus

I'm from the Robusta team (https://github.com/robusta-dev/robusta) which bursts upwards towards the end. Happy to answer any questions!

The guys at Robusta, added it into thier slack so when alerts pop of issues in k8s, chatgpt can be used to investigate and offer options to check and potentially solutions. Next phase is probably to let it also apply it :)

It's no replacement for learning how things work, but we're trying to automate common troubleshooting cases with Robusta. https://github.com/robusta-dev/robusta

https://docs.robusta.dev/master/ https://github.com/robusta-dev/robusta

This is the sort of thing we built Robusta for: https://github.com/robusta-dev/robusta

kubectx: brew install kubectx

default is where any actions which require a namespace will go into if one is not explicitly defined in a default setup (tools such as kubens can alter this behavior). In the context of Jenkins, namespaces are a useful way to allow isolation of individual Jenkins instances that want to utilize the same Kubernetes cluster. Creation of a namespace is a simple option to kubectl:

Here you go: https://github.com/ahmetb/kubectx and https://kubecm.cloud/

check out kubectx/kubens https://github.com/ahmetb/kubectx very handy tool to permanently switch context/namespace

kubectx + kubens v0.9.4

For a peek at what's currently possible, visit the documentation site, in particular the Usage section. For this initial release, it has feature parity with kubectx and kubens and that's about it, but there's lots of room for growth.

I also encourage you to install kubectx + kubens to navigate Kubernetes easily.