kubectl
kubectx
Our great sponsors
kubectl | kubectx | |
---|---|---|
13 | 40 | |
2,684 | 16,894 | |
1.8% | - | |
9.2 | 3.3 | |
3 days ago | 12 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kubectl
-
What are these orphaned PVC objects?
Check https://github.com/kubernetes/kubectl/issues/151
-
Setting kubectl context via env var
I have read this issue, and up to now it seems not possible to change the kubectl context via an env var: https://github.com/kubernetes/kubectl/issues/1154
-
Deciding between Rust or Go for desktop applications
However, I would encourage people to take a look at what the code looks like before assuming the Go developer experience on this was positive. Bear in mind that's just the top level kubectl command and some helper functions, the subcommand definitions take up a several more files split into a few more packages. Then you're still not even done, because code that uses the parsed flags still has to redundantly check things that couldn't be enforced at the type level, something Go folks like to pretend is a good thing for some reason.
-
Recommendations on file/dir/module structure, common dependencies, and/or anti-patterns for writing CLI tool in Rust
kubectl is for sure battle tested, but it involves very Kubernetes specific implementations and is going to be too complicated for the first pointer
- Recommendations on building a simple DSL REPL?
-
Why Go and Not Rust?
> context.Background() is typically only used when one doesn’t care about the result. If you did care about the result, you should be passing the parent context to preserve the circuit breaker timeout in case the operation takes too long.
Not necessarily. You would use context.Background in a test situation. It's also commonly used for short-lived applications like a CLI invocation. You can see kubectl uses context.Background quite a lot: https://github.com/kubernetes/kubectl/search?q=context.backg...
> I think the level of pain you experience from mutable references in Rust depends on if you’re coming from an OOP or FP background. I have a FP background and so the patterns I use to build code already greatly restrict mutation. You can usually change code that updates data immutably (creating a new copy of it) with mutable code in rust because the control flow of your program already involves passing that new version back to the caller which also satisfies the borrow checker in most situations.
There has to be a better solution to needlessly copying data.
-
kubectl - Create PV/PVC
This is particularly useful for academic purposes, and makes somehow convinient to get the yaml template of k8s objects. I was looking for this as well due to an upcoming ckad test i have. Unfourtunately due to not being considered best practice the request for it was dismissed. https://github.com/kubernetes/kubectl/issues/1073
-
Must `kubectl apply` twice to allow CRD usage?
I see, apologies, I did misunderstand. This is actually a known race condition between kubectl (or even helm, or any Kube API client) issuing the requests to deploy CRs that depend on CRDs while those CRDs are still being installed on the API server. Simply put, kubectl makes these requests too quickly. There is no solution to this currently aside from deploying CRDs separately from the resources they expose. See this kubectl issue: https://github.com/kubernetes/kubectl/issues/1117, and there are some links in the comments to other issues echoing the same problem in helm and elsewhere.
-
What's the number one annoyance that drives you crazy about Kubernetes?
Go add --no-really-all if you really want it: https://github.com/kubernetes/kubectl
-
How to change a POD label via client-go?
You could take a look at how kubectl actually does it: https://github.com/kubernetes/kubectl/blob/master/pkg/cmd/label/label.go
kubectx
-
Building a Kubernetes Operator with the Operator Framework
kubectx: brew install kubectx
-
Jenkins Agents On Kubernetes
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:
-
Tool to manage kubeconfig configurations
Here you go: https://github.com/ahmetb/kubectx and https://kubecm.cloud/
-
Setting kubectl context via env var
check out kubectx/kubens https://github.com/ahmetb/kubectx very handy tool to permanently switch context/namespace
- Minikube broke my Kubectl config
- Managing local cluster config
-
How to Deploy and Scale Strapi on a Kubernetes Cluster 1/2
kubectx + kubens v0.9.4
-
[ANN] Kele: Snappy Kubernetes cluster management in Emacs
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.
-
Injecting secrets from Vault into Helm charts with ArgoCD
I also encourage you to install kubectx + kubens to navigate Kubernetes easily.
- What daily terminal based tools are you using for cluster management?
What are some alternatives?
helm - The Kubernetes Package Manager
fzf-tab - Replace zsh's default completion selection menu with fzf!
robusta - Kubernetes observability and automation, with an awesome Prometheus integration
kubie - A more powerful alternative to kubectx and kubens
kubernetes - Production-Grade Container Scheduling and Management
kubeswitch - The kubectx for operators.
client-go - Go client for Kubernetes.
kubecm - Manage your kubeconfig more easily.
cli - GitHub’s official command line tool
kubectl-neat - Clean up Kubernetes yaml and json output to make it readable
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..
kubectl-trace - Schedule bpftrace programs on your kubernetes cluster using the kubectl