Right now, requiring users to understand every field in a deployment manifest feels unnecessarily complex. Since Kubernetes YAML is already quite straightforward to copy, paste, and modify from examples, the added cognitive load of deciphering each field may not provide proportional value—especially when the same manifests can be generated more efficiently.
What would be far more valuable is a feature that lets users import a Helm chart URL directly into the UI, then visualize and interact with the chart’s values in an intuitive way—no need to dig through documentation. Being able to explore, modify, and export the values in a user-friendly interface would save significant time and reduce friction, especially when working with complex or unfamiliar charts.
In short: instead of manually parsing YAML or hunting through Helm docs, a visual, interactive view of Helm values—especially when tied to a chart URL—would be a game-changer for productivity and usability.
Thank you for the insight, for the initial version I wanted something that laid down the groundwork for defined schemas. I also wanted to make sure that I handled data conversion from yaml -> json object -> yaml correctly.
I love the idea to be able to import helm url's (and possibly edit + rehost), the next features are going to be around naming required/most used fields for simplification and decluttering the node components, and adding in support for helm and kustomize with template variables.
Was there anything else that you noticed that you would like to see or anything that you saw that you enjoyed?
A few years back, I had an idea for a K8s YAML explainer. In the spirit of XSLT transforms on XML, you would run your K8s yaml against an explainer file and generate a document that provided visualizations, interpretative text alongside the define values and an explanation about the field, its purpose, suggestions and some best practices about the field. Used the idea to write my first rust CLI. I was heading towards using it for Helm, but never got to it.
An object graph solution perhaps? : https://codesolvent.com/configr/
You can go from data format (yaml,json,xml, property file...etc) to object graph and the reverse.