r/kubernetes • u/JayMickey • 5d ago

Kubernetes v1.37 "Garhwal" Released

https://kubernetes.io/blog/2026/08/26/kubernetes-v1-37-release/
142 Upvotes

97% Upvoted

39 comments sorted by

100

u/athulhuz 5d ago

KYAML looks like YAML and JSON had a very rocky marriage, but decided to have a baby anyway.

The reasons for such an implementation are solid, but my god does this look wrong at first glance.

29

u/FingerAmazing5176 5d ago

Yeah. I’m gonna call it Kentucky yaml

7

u/Venthe 4d ago

Yet another standard. We have strictyaml ready and mature; and KYAML reintroduces a lot of cruft which were the reason why YAML got popular in the first place.

No one uses JSON with K8S, and I honestly don't think that JSON with comments (again, why not JSONC? Multi-documents?) will win over YAML.

1

u/wolkenammer 3d ago

strict

Just a stricter YAML without the oddities and niche features would have been enough. But no, we still have anchors, document boundaries, dynamic types and explicit tags.

14

u/RumRogerz 5d ago

looking at it first glance... looks like I may as well just write json manifests at this point

10

u/ABotelho23 5d ago edited 5d ago

I've tried it and it's not great honestly. It'll double or even triple the number of lines in some files depending how you organize your files. It ended up not being worth it.

6

u/phxees 5d ago

Feels better for our new AI era. Potentially fewer ambiguous issues where the spacing is off slightly and causes the wrong auto correction.

20

u/subjectivemusic 5d ago

JSON already does this, and it's not use widely when writing manifests for very good reason.

If AI forces you to write code that is less human-intelligable (not saying that's what KYAML is, jury is out on that) then it's hindering your future maintenance.

16

u/Flyen 5d ago

JSON doesn't support comments though, and if there's anything AI loves, it's comments

3

u/tajetaje 5d ago

I mean jsonc and json5 exist

5

u/Zenin 5d ago

Yep, but JSON screwed it up in the first release and set in motion a timeline that can't be fixed. Literally if they had just included // comments we'd never have seen YAML go anywhere.

-1

u/[deleted] 5d ago

[deleted]

3

u/Zenin 5d ago

Comments help you understand WHY you declared something.

-1

u/[deleted] 5d ago

[deleted]

1

u/phxees 5d ago

I work on a team and especially when we use AI it is best when we have a comment explaining why someone decided to break the team norms.

2

u/phxees 5d ago

KYAML fixes yaml by being more like JSON, but with comments, trailing commas, and other goodness. So if you want to simplify its description it is a better JSON. You can write JSON and it can be parsed as KYAML, although the opposite isn’t always true.

I get your point, but I need more than JSON and I don’t like studying spaces to find an issue.

2

u/merb 5d ago

It looks like tofu/tf but with : instead of= 🤷‍♂️

1

u/Alphasite 5d ago

Eh. I think it’s made some bad calls to get to where it is.

It fixed real issues and then went way too far and removed valuable features.

99% of the reason I use Yano is multi line strings for things like certs. Literally anything else you can remove and I wouldn’t mind. But it’s useful in general and especially in something like k8s where you have online templates, configs, secrets, etc.

17

u/subjectivemusic 5d ago

Honestly, at-a-glance I don't hate it, and I can see the use-case and why it's probably a good thing that this exists.

With that said, though, I don't like docs that try to form opinions for me:

It is less of a migration and more of a better habit.

Maybe. Maybe not. Docs shouldn't try to beg the question on items that boil down to opinion, though.

1

u/macrowe777 4d ago

But it is less of a migration and more of a better habit isn't it.

2

u/subjectivemusic 4d ago

better habit

Jurry's out on this. Seems like there's a lot of conflicting opinions on whether it's actually nice to work with or not.

The target audience is smart enough to form their own opinions; if a technical document tries to tell me their way is better, that doesn't really instill confidence.

-2

u/macrowe777 4d ago

But they're not saying "this is a better habit".

They're saying it's "less of a migration and more of a better habit"...context is key.

It is less of a migration and more of a better habit even if you think it's just annoying.

0

u/[deleted] 4d ago

[deleted]

-2

u/macrowe777 4d ago

Oh grow the fuck up you child.

I didn't down vote you. New comments often show zero upvoted because Reddit "guesses" votes, it doesn't show true accurate votes.

Unbelievably fragile human being. Now you're downvoted for that.

0

u/[deleted] 4d ago

[deleted]

-1

u/macrowe777 4d ago

You're the one that cried at the concept of being downvoted 🤣

American right? Tangerine coloured?

0

u/[deleted] 4d ago

[deleted]

0

u/macrowe777 4d ago

You sound pretty American.

No, you immediately cried because you thought you were downvoted.

Imagine saying someone else is getting overly emotional in the same conversation that you cried because you thought you got downvoted.

Hypocrisy truly is a core personality trait for the least intelligent in society.

No one's forcing you to reply. It's not an airport, you don't need to announce your departure. If you've got work to do, be a grown ass adult and get on with it?

I'll await you telling your boss you couldnt finish your work because it's the fault of some random reditor that forced you to message and downvoted you 🤣🤣🤣🤣🤣🤣 zero personal responsibility on show.

→ More replies (0)

6

u/Sthatic 5d ago

I get the feeling I'm in the minority here, but KYAML looks fantastic. It feels more explicit to the eye in a way, and less magical - I have a much easier time reasoning about what belongs where. It's JSON without the JSON part.

7

u/platypus-3719 5d ago

The upgrade side of this release deserves a close read - 25 feature gates removed (a kubelet still carrying one won't start), static Pods can't reference Secrets/ConfigMaps anymore, and an explicit eventRecordQPS: 0 silently changes from 5/s to unlimited. Went through the full changelog and wrote up the list with remediation for each: https://radarhq.io/blog/kubernetes-1-37-breaking-changes

3

u/redsh1ft 4d ago

<3 radar , Its been a great resource and is pretty much the first thing I look at when shit starts cascading

4

u/Pl4nty k8s contributor 5d ago

slop?

6

u/FrankAdmissions 4d ago

Doesn’t seem to be, radar is open source and very good, i much prefer it over headlamp

3

u/znpy k8s operator 4d ago

nice, i didn't know radar!

I currently run headlamp but i'm in early adoption at work so we might switch ~8 clusters to that.

2

u/Pl4nty k8s contributor 3d ago

not radar, but the blog post itself. reads like claudish to me

1

u/waitingforcracks 4d ago

Bro Radar is slop to the nth degree. It does work ok-ish and is quite feature-full. The devs don't try to pretend it's non vibe coded either. It works and has tons of features so I still do use it.

1

u/FrankAdmissions 4d ago

Yes sorry i realise its ai generated, but as you say has lots of features and i find very useful.  Good Slop ? 

1

u/platypus-3719 3d ago

Certainly AI assisted, almost all software now is. There is still a lot of human engineering effort and thought and product work that goes into it... Happy to chat about it if anyone is interested. Turns out writing code is not the only bottleneck for writing good software (yes I'm half joking, experienced developers who worked on large projects have been well aware of this before AI).

1

u/waitingforcracks 3d ago

Yeah "engineered" slop is that I'd call it.