client-go
charts
client-go | charts | |
---|---|---|
38 | 30 | |
8,619 | 1,367 | |
1.0% | - | |
9.2 | 9.7 | |
8 days ago | over 1 year ago | |
Go | Smarty | |
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.
client-go
-
The Inner Workings of Kubernetes Management Frontends — A Software Engineer’s Perspective
The Kubernetes clients (e.g., Go client) support developers with both methods to connect to a cluster, as we can see in the following examples.
-
Has anyone ever tried to learn how k8s works?
My suggestion would be to start looking at things like https://github.com/kubernetes/client-go first in order to get a feel for the API and how data plane k8s components interact with the apiserver (it's the same thing that kubelet uses). Then move on to trying to build your own k8s operator to get a feel for how people expand and customize k8s functionality without having to modify upstream at all. IMO the codebase itself is too messy and in constant flux to make too much sense of it unless you are planning to contribute to upstream.
-
Can't override Kubernetes config in Kubernetes Go client
GitHub related issue https://github.com/kubernetes/client-go/issues/735
-
CUE compared to helm/kustomize...
CUE is cool and all but as soon as I start writing real code structures I want to reach for client-go.
-
Go 1.21 will (probably) download newer toolchains on demand by default
I'm... really not sure I agree with this, from a philosophical point of view. It feels like this is making "eh, we'll just upgrade our Go version next quarter" too easy; ultimately some responsibility toward updating your application's Go version to work with what new dependencies require should fall on Us, the application developers. Sure, we're bad at it. Everyone's lived through running years-old versions of some toolchain. But I think this just makes the problem worse, not better.
Its compounded by the problem that, when you're setting up a new library, the `go` directive in the mod file defaults to your current toolchain; most likely a very current one. It would take a not-insignificant effort on the library author's part to change that to assert the true-minimum version of Go required, based on libraries and language features and such. That's an effort most devs won't take on.
I'd also guess that many developers, up-to this point if not indefinitely because education is hard, interpreted that `go` directive to mean more-of "the version of go this was built with"; not necessarily "the version of go minimally required". There are really major libraries (kubernetes/client-go [1]) which assert a minimum go version of 1.20; the latest version (see, for comparison, the aws-sdk, which specifies a more reasonable go1.11 [2]). I haven't, you know, fully audited these libraries, but 1.20 wasn't exactly a major release with huge language and library changes; do they really need 1.20? If devs haven't traditionally operated in this world where keeping this value super-current results in actually significant downstream costs in network bandwidth (go1.20 is 100mb!) and CI runtime, do we have confidence that the community will adapt? There's millions of Go packages out there.
Or, will a future version of Go patch a security update, not backport it more than one version or so, and libraries have to specify the newest `go` directive version, because manifest security scanning and policy and whatever? Like, yeah, I get the rosy worldview of "your minimum version encodes required language and library features", but its not obvious to me that this is how this field is, or even will be, used.
Just a LOT of tertiary costs to this change which I hope the team has thought through.
[1] https://github.com/kubernetes/client-go/blob/master/go.mod#L...
[2] https://github.com/aws/aws-sdk-go/blob/main/go.mod
-
How to list all kubernetes objects with specific label using client-go
I looked at dynamic package, but it seems like it needs GroupVersionResource, which is different for, say, Service objects and Deployment objects. Also when I pass schema.GroupVersionResource{Group: "apps", Version: "v1"} it doesn't find anything, when I pass schema.GroupVersionResource{Version: "v1"} it finds only namespace object and also doesn't looks for labels, though I provided label options:
-
What's the best way to get notified when kubernetes Deployments change using the k8s.io/client-go library?
I'm writing a script that uses the k8s.io/client-go library (godocs here) to manipulate Deployments. In particular, I want to add a label selector to every Deployment in my cluster. Deployment label selectors are immutable. So my approach is to:
- K8S Get deployment liveness probe status
-
Learning kubebuilder - good examples of Golang watching/manipulating k8s objects?
Actually, kubebuilder is not using the standard Go libraries, but one using reflection to dynamically resolve the client based on the type you hand it (which is arguably better). The "official" client is k8s.io/client-go.
-
My LFX Mentorship experience with OpenELB
Then on June 18th, 2022, I got a chance to meet our mentors and the other mentee of OpenELB (the mentee and the mentors of OpenFunction were also there). There I was informed about how to start working on the project, so I started learning about using the Kubernetes API client. After experimenting with the official Kubernetes Client, I learned that it's not very feasible to use that for dealing with CRDs (custom resource definitions), so I explored the controller-runtime client as per what I found in many sources, and found that it was a great fit for the backend of our project. During that time, I also built a simple project to see if everything would work as expected or not (as this was the first time I dealt with a Kubernetes client, I considered that debugging would be easier in a smaller project).
charts
- Helm charts that bundles basic home server apps?
-
Getting Started with Kubernetes Questions
Spinning up workloads in kubernetes is much different than just spinning up a container in docker or even with docker compose. If someone has not already packaged it in a helm chart or some other kubernetes workload you'll have to develop one yourself. There are some nice library charts you can use as a base that should handle just about any random docker image you want to deploy. https://github.com/bjw-s/helm-charts/tree/main/charts/library/common there is also a repo of pre developed charts for common images. https://github.com/k8s-at-home/charts but be aware it was recently deprecated so it won't be receiving any updates.
-
Advice on system design best practices?
Take a look at https://github.com/k8s-at-home/charts (recently deprecated but still a fantastic resource) - there are charts for the popular Arrs , tools, etc. You could deploy each chart individually into a namespace, or you could create yourself an "umbrella" chart which pulls in all the necessary charts as dependencies.
-
With multiple custom apps, how do you manage your Helm charts?
Library charts. A very thorough example can be seen here and usages of it here.
-
Running into a problem with the k8s-at-home pod-gateway where the gateway-init container that's bootstrapping selected namespaces is unable to reach cluster DNS while pods in other namespaces can. Anyone run into this before?
Could it be related to this? https://github.com/k8s-at-home/charts/pull/1435/files
-
Struggling with Fireflyi-III installation
I'd submitted a helm chart at https://github.com/k8s-at-home/charts/tree/master/charts/stable/firefly-iii if you want to try out
- Plex on Kubernetes with hardware decoding... Victory
-
[Help!] K3s Sonarr failing with X509CertificateValidationService due to expired LetsEncrypt cert in Mono
I know /u/stefantigro means well but the way you are both doing the helm charts is not ideal, helm charts are meant to be shared, not as a means to install apps into your cluster from a local folder. While they can be, it's not a good pattern. Take the helm chart from here for example. This is a published helm chart you can install using the commands in the Readme and you only need to provide the configuration for your instance from the values.yaml file. You can take a look at the values I use for this helm chart here. You can also see I'm using an custom Sonarr image, this image is tailored to running in Kubernetes
-
Bounty for Homebridge TrueChart
There is a working Helm chart for k8s-at-home that should be a good starting point. The biggest hurdle I see is that homebridge can conflict with SCALE's mDNS service as seen in this linked post.
-
Been self-hosting close to half a year now. All running on a k3s cluster of raspberry pis. Thank you to this subreddit for all the help and great ideas!
There's an actual helm chart published here.
What are some alternatives?
kubebuilder - Kubebuilder - SDK for building Kubernetes APIs using CRDs
truecharts - Community App Catalog for TrueNAS SCALE [Moved to: https://github.com/truecharts/charts]
controller-runtime - Repo for the controller-runtime subproject of kubebuilder (sig-apimachinery)
kube-plex - Scalable Plex Media Server on Kubernetes -- dispatch transcode jobs as pods on your cluster!
kustomize - Customization of kubernetes YAML configurations
MagicMirror - MagicMirror² is an open source modular smart mirror platform. With a growing list of installable modules, the MagicMirror² allows you to convert your hallway or bathroom mirror into your personal assistant.
celery - Distributed Task Queue (development branch)
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
apimachinery
frigate - Frigate is a tool for automatically generating documentation for your Helm charts
k3s - Lightweight Kubernetes
kubevirt - Kubernetes Virtualization API and runtime in order to define and manage virtual machines.