This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

/hold
/label needs-ok-to-test

@rikatz: The label(s) /label needs-ok-to-test cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, ci-short, ci-extended, ci-full, official-cve-feed. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

We should start with etcd first

I would rather migrate etcd to Perl and make it a k/v regex database

make sure to make cherry picks for the previous branches too. I'll LGTM and approve immediately.

Which AI tool are you using to make this conversion? Looks like a weekend project to rewrite either way

Exactly, no AI is needed, just me, a bucket of coffee and some free time during my weekend.

I can’t wait to write Kubernetes TOML

Wth is this 😂

Start by introducing the most important module: age verification for each kubectl apply.

/kubernetes merge it to main 😂

Wasn't the goal to write it to assembly for performance gains* claude max pro will do it.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dkanas, rikatz, shlomitubul
Once this PR has been reviewed and has the lgtm label, please assign liggitt for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

/kubernetes merge it to main 😂

I am sure @rohitg00 will be the one to do the actual migration

🦀

I was shocked for a while, then realised it's 1st of April today XD

https://en.wikipedia.org/wiki/Carcinisation

Just ask the AI to rewrite everything into plain C, they are so smart nowadays that they will write perfect code without bugs or security issues, GUARANTEED!!! :-D

And call it Kubernetes 2.0.0, it's about time!

+1 from me, great job @rikatz! 🙏🙏🙏

After a successful launch after the weekend, let's prioritize rewriting kubernetes-sigs. I volunteer to help with Gateway API.

I would start with something less important than Gateway API on kubernetes-sigs, like controller-runtime. I am sure @sbueringer would approve it

Perhaps it's also the right time to replace KubeDNS with generative AI DNS, which you've been planning for some time, @Michcioperz?

Guys, if you're serious about tacking this project, I will be happy to participate. However, I need to clarify a few points first.

What underlying OS are you considering? Is it an immutable one? We will need a better alternative to etcd. Are we prepared to develop a superior option that includes multisite, multicluster capabilities, an improved consensus protocol, robust backup and recovery systems. The project must be ready to support algorithms that enable post-quantum cryptography? Will it support HTTP/3 as the default? Are you planning to allow current operators to run on top of the platform, or are you aiming to create a new ecosystem? Will eBPF be the default for networking and observability? How many architects will you bring onto the team? Who will be tasked with creating extensive documentation? Are you planning to incorporate LLMs into this project, and what type of license are you considering? Will you create a completely new fork? How do you plan to fund the project and generate revenue? Thank you very much!

troublemaker ricardo 😄

thanks @rikatz this was a lot of fun :)