Post

Not a lot of people know this, but we can actually go to Kubernetes 2.0 basically whenever. We just push it back by a year every time someone asks, like Valve does with Half-Life 3

11/9/26, 4:04 pm5 reposts70 likes

fry69

@fry69.dev

13 Sept

Ditch numbered versions and go straight to monthly/quarterly/yearly releases?

Marly Salazar

@secant2.bsky.social

11 Sept

Every time someone asks for a new flag for kubectl create we add 6 more months to the backlog plans for adding colored output.

kat cosgrove

@kat.lol

11 Sept

I love this for us, as a project

Olivier Bourgeois

@olivi-eh.dev

11 Sept

Low-key I can't live without kubecolor and I wish it was built-in 😔

github.comGitHub - kubecolor/kubecolor: Colorize your kubectl outputColorize your kubectl output. Contribute to kubecolor/kubecolor development by creating an account on GitHub.

John Breen

@breen.tech

11 Sept

Will it be called Twobernetes?

28s

Or even 2bernetes?

Twobernetes, Or not twobernetes, That is the question.

Nicholas Macias

@nich.bsky.social

12 Sept

Kubernethrees… you are onto something

Erica Van Houten

@epvh.bsky.social

11 Sept

Real bravery is just calling every release a breaking release.

Sagittarius A*

@sagastar.bsky.social

11 Sept

what would you call it k8s2

k9s

k8s t1o