Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.
This week we’re going to talk about YAML, the markup language that’s driving most of the cloud native app world.
1. YAML is everywhere. 15 years ago it was mostly found in configuration files for Ruby on Rails apps. Nowadays? Crazy. Docker Compose? Check. Kubernetes deployments? Check. Ansible playbooks? Check. Antora playbooks? Check (although these can also be written in TOML, did you know?) GitLab CI/CD pipelines? Check. Azure pipelines? Check. Great! Right? No, not really; Martin Tournoij has kept a very interesting list of awful YAML facts well worth a read.
2. Many of us are quite happy with the YAML plugin by Red Hat for Visual Studio Code, but if you are a Vim user busy editing Kubernetes configuration files day and night, this article will certainly make your day.
3. We always wanted to write a clickbait headline in a VSHN.timer article, so here it goes: „How many ways are there to break a multi-line string in YAML? The answer might surprise you.“
5. If you reached the point of YAML saturation, you might want to give the CDK for Kubernetes a try. It helps you write manifests using Python and TypeScript instead of YAML. Because no problem can’t be solved with yet another level of abstraction.
Does your team get along well with YAML? Or have they wrapped it with yet another abstraction layer? Do you have any tips you would like to share with the community? Get in touch with us through the form at the bottom of this page, and see you next week for another edition of VSHN.timer.