Kubernetes YAML Generator

I wonder what the need for tools such as this or other &quot;Kubernetes-by-example&quot; type pages tell us about the complexity of configuring Kubernetes resources.<p>Do we need a better layer of abstraction, i.e. better adoption and tighter integration for something like kustomize? Have we fucked up completely with Kubernetes due to it being outrageously complicated for simple tasks? How we redesign this to be simpler? Is the complexity even a problem for the target audience?<p>I&#x27;ve no idea. I just know I&#x27;m a kubernetes admin and I can&#x27;t write a deployment yaml without googling or copy&#x2F;pasting.

Super cool to see these sorts of tools. They&#x27;re great for learning the kube API.<p>For production-y things however, some meta-config language that allows deterministic templateing would be a huge improvement. It allows you to make sweeping&#x2F;uniform infrastructure changes from a single library or tool change.<p>Kubecfg is a good example of the basics one could implement [0] although it&#x27;s examples aren&#x27;t as fully fledged and organized as they could be.<p>[0] - <a href="https:&#x2F;&#x2F;github.com&#x2F;bitnami&#x2F;kubecfg&#x2F;blob&#x2F;master&#x2F;examples&#x2F;guestbook.jsonnet" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;bitnami&#x2F;kubecfg&#x2F;blob&#x2F;master&#x2F;examples&#x2F;gues...</a>

We&#x27;re using Pulumi <a href="https:&#x2F;&#x2F;www.pulumi.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.pulumi.com&#x2F;</a> to do our K8 configuration.<p>We can use TypeScript interfaces (which give us nice ide code completion) to define our yaml.<p>we can then create functions where we would normally duplicate Yaml. Really nice. <a href="https:&#x2F;&#x2F;www.pulumi.com&#x2F;kubernetes&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.pulumi.com&#x2F;kubernetes&#x2F;</a>

We built this internally to test that the UI we built for Kubernetes deployments was producing the expected YAML. Thought it would be useful to share.

I don’t know how to feel about Kubernetes configuration apparently being so complicated that you need a generator for it, instead of just having the docs and your IDE open in split screen like with Docker Compose.<p>That said, this still looks cool. I just hope we won’t need a Kubernetes configuration generator generator anytime soon.

Would be nice to have a linter or something that you know is best practice. Eg if you check your yaml and its more complex than it could be.

That looks super handy! It seems like it&#x27;d be possible to &quot;port&quot; to VSCode. Some other comments mention autocomplete in VSCode, but it&#x27;d be nifty to run something like this directly in the VSCode UI.

We built a similar thing and used in our graphical k8s designer : <a href="https:&#x2F;&#x2F;k8od.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;k8od.io&#x2F;</a>.

Ooooh nice! When I saw the title I was hoping this is what it would be. I&#x27;d dreamed of building something like this, but never had the time or the buy in.<p>Aside from making it easy to generate k8s manifests, this could also be a great learning tool. If you allowed this to generate multiple resources that are linked, it could be a great illustration of how different resources fit together.

This is awesome. It is so easy to make mistakes when configuring your k8s services

Awesome work for the deployment resource! Now do this for all the other native k8s types and popular custom resources. :)

It would be nice if the tool could &quot;import&quot; an existing YAML and show the resulting configuration in the GUI.

Awesome! Was waiting for someone to build it :-)

This is great, thank you!

Looks very useful. In my opinion the configuration format should have been built like this from the get go.<p>Clear schema (like TypeScript interfaces or something similar) which allows generating an UI.