metacontroller
kubectl
metacontroller | kubectl | |
---|---|---|
15 | 13 | |
777 | 2,688 | |
1.7% | 0.7% | |
8.5 | 9.2 | |
5 days ago | 1 day 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.
metacontroller
- What Is A Kubernetes Operator?
-
Why is Kubernetes adoption so hard?
It worth adopt proper controller development with something like Metacontroller, Kopf or Java Operator SDK.
- What is your approach to adding custom labels to a pod in a deployment that's managed by a helm chart?
-
is there a way to set expiry date for k8s rbac setting?
There are many frameworks, like the Operator Framework (https://operatorframework.io/) to the MetaController (https://github.com/metacontroller/metacontroller) to KubeBuilder(https://github.com/kubernetes-sigs/kubebuilder) to the Kubernetes Operator Framework (kopf, https://kopf.readthedocs.io/en/stable/), among others.
-
Is there a tutorial on how to write an Operator in Go?
You might like a little alternative to writing your own in the first instance:) take a look at https://metacontroller.github.io/metacontroller/
-
Writing an Operator from scratch
Codegen is not magic, but if you want to make it simple stupid, supportable and prod-usable I'd go for metacontroller. There's not much magic to it - just common admission/validation webhooks propagated to your controller implementation, alongside the simplest possible reconciliation cycle. We had adopted Knative driven metacontrollers and it's a pretty solid approach.
-
For what should I take a look?
https://github.com/metacontroller/metacontroller - Sounds cool! I will look into it.
-
Dynamic Mutating Pod Admission Controller?
When I need a quick mutating controller, I like to use MetaController, which makes rapid prototyping really easy: https://metacontroller.github.io/metacontroller/
-
Best option to write a CRD today?
If you are more into lightweight and common use cases, look at metacontroller or the shell-operator.
-
What's the number one annoyance that drives you crazy about Kubernetes?
In case you've not heard of it, the metacontroller aims to do exactly this. It provides the controller-lifecycle (registering your types, watching the API for changes, etc), you just need to provide a HTTP webhook to receive the JSON object, and respond with the modifications\resources you want.
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
What are some alternatives?
shell-operator - Shell-operator is a tool for running event-driven scripts in a Kubernetes cluster
helm - The Kubernetes Package Manager
minikube - Run Kubernetes locally
robusta - Kubernetes observability and automation, with an awesome Prometheus integration
kubernetes - Production-Grade Container Scheduling and Management
akrobateo - Akrobateo is a simple Kubernetes operator to expose in-cluster LoadBalancer services as node hostPorts using DaemonSets.
client-go - Go client for Kubernetes.
k8s-bigip-ctlr - Repository for F5 Container Ingress Services for Kubernetes & OpenShift.
cli - GitHub’s official command line tool
keepalived-operator - An operator to manage VIPs backed by keepalived
Mattermost - Mattermost is an open source platform for secure collaboration across the entire software development lifecycle..