Kubernetes dev moment

368 points · 9 comments · view on lemmy.world

9 Comments

thejml@lemm.ee · 22 pts · 2y (2 replies)

Don’t forget, Kubernetes is totally happy with json input and output instead. Use json, be the change you want to see in the world!

SnotFlickerman@lemmy.blahaj.zone · 9 pts · 2y

Press X to "Jason!"

4z01235@lemmy.world · 9 pts · 2y

That's because YAML syntax is a superset of JSON. Any YAML parser should also accept JSON, not just the one k8s uses.

joshzcold@lemmy.world · 15 pts · 2y (3 replies)

Add on a CI system (not Jenkins) and you got yaml controlling your yaml!

averagedrunk@lemmy.ml · 11 pts · 2y (1 reply)

My last job is currently controlling kubernetes with Ansible (configuration management and orchestration) in a hybrid cloud model. The new engineering director likes yaml so they put yaml on his yaml.

Azzk1kr@feddit.nl · 2 pts · 2y

Yo dawg...

vojel@discuss.tchncs.de · 2 pts · 2y

Wait I do that and never realized it. YAMLception

shyguyblue@lemmy.world · 13 pts · 2y

If yaml wasn't such a pain to edit on mobile, I wouldn't mind it so much. Yes, XML uses closing tags, but it's the 2020's, I think we can stand that extra few K of space so I can edit my portainer stacks without the UI freaking the fuck out because I want to delete something. YMMV...

342345@feddit.de · 5 pts · 2y

It felt unusual at first that they attached semantics to (white spaces and tabs as) non-printable characters. On the other hand other n.p.- characters like line feeds always had a meaning (I.e. within multi line strings).

So why not, when it helps to reduce the amount of (printable) characters to describe your thing and increase clarity? 🤔