News for hackers. Stuff that matters.
Re:What Would a Kubernetes 2.0 Look Like by fragmede on Thursday June 19, 2025 @03:11PM (#44321586)
Instead of yaml, json, or HCL, how about starlark? It's a stripped down Python, used in production by bazel, so it's already got the go libraries.
Re:What Would a Kubernetes 2.0 Look Like by mdaniel on Thursday June 19, 2025 @03:38PM (#44321830)
As the sibling comment points out, I think that would be a perfectly fine helm replacement, but I would never ever want to feed starlark into k8s apis directly
Re:What Would a Kubernetes 2.0 Look Like by dilyevsky on Thursday June 19, 2025 @11:39PM (#44324518)
Not directly, first render it to protos. Couple gigs ago I made this - https://github.com/cruise-automation/isopod
Re:What Would a Kubernetes 2.0 Look Like by fjasdfwa on Thursday June 19, 2025 @03:31PM (#44321771)
kube-apiserver uses a JSON REST API. You can use whatever serializes to JSON. YAML is the most common and already works directly with kubectl.

I personally use TypeScript since it has unions and structural typing with native JSON support but really anything can work.

Re:What Would a Kubernetes 2.0 Look Like by mdaniel on Thursday June 19, 2025 @04:48PM (#44322407)
Fun fact, while digging into the sibling comment's complaint about the OpenAPI spec, I learned that it actually advertises multiple content-types:

  application/json
  application/json;stream=watch
  application/vnd.kubernetes.protobuf
  application/vnd.kubernetes.protobuf;stream=watch
  application/yaml
which I presume all get coerced into protobuf before being actually interpreted