kubernetes

client-go

Go2018–2024

kubernetes / client-go

client-go

Go client for Kubernetes.

Systems & Infrastructure DevOps & Cloud

Explore on GitHub Read Hacker News discussions

6Distinct people

6Mentions

0Explicit recommenders

9.9KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Go client for Kubernetes.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2018-08-20 04:09:30 UTC to 2024-12-10 17:47:14 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	1	1
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	0	0
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	2	2
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	1
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	1	1

What Hacker News says

6 sources

mdaniel·Dec 10, 2024

In kubernetes having "version one, minor whatever" isn't meaningful because I can assure you with absolute confidence that 1.2 != 1.30 so it would be helpful to include the actual, no kidding, minimum version that you support https://www.dash0.com/documentation/dash0/dash0-kubernetes-o... Chasing https://github.com/dash0hq/dash0-operator/blob/0.35.3/go.mod... into https://github.com/kubernetes/client-go/tree/v0.31.3#compati... doesn't even mention any of the 1.30+ series but based solely upon the .31 part it sure does seem like it's a bleeding edge client-go

In Show HN: Dash0 – Dev-Friendly OpenTelemetry Observability with Open Standards

015a·Jun 24, 2023

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 su

Read the rest

ch. 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

In Go 1.21 will (probably) download newer toolchains on demand by default

scrubs·Jul 14, 2021

Coincidentally, it seems like this part of the solution: https://github.com/kubernetes/client-go

In Ask HN: Kubernetes API?

debarshri·Jun 21, 2021

One of the fun things I recently did was re-implementing it kubectl exec in client-go following a github [1]. Fun challenge is to then convert it into a websocket or http handler. [1]https://github.com/kubernetes/client-go/issues/809

In How does 'kubectl exec' work? (2019)

podoman·Jul 22, 2020

At the moment, we're generating manifests via the kubernetes API. This may change though! Take a look: https://github.com/kubernetes/client-go

In Launch HN: Reploy (YC S20) – Instant fullstack staging environments for web apps

atombender·Aug 20, 2018

Note that the Kubernetes people tried to migrate to Dep, but weren't successful. As I recall, it was due to several blocking issues (e.g. see https://github.com/kubernetes/client-go/issues/7).

In Introduction to Go Modules