Live data from Hacker News

Tilt – Local Kubernetes development with no stress

github.com

1–10 of 76 posts

Re: Tilt – Local Kubernetes development with no stress

#5
post #2

Uuuuh not using YAML. Controversial. (in the docker/k8s ecosphere, where YAML seems ubiquitous) I don't love YAML though I am not sure Starlark looks any more readable. YACL => Yet another config language...?

> Uuuuh not using YAML

That's not what it says. Maybe next time you can try to understand before you comment.

And YAML sucks, by the way.

Re: Tilt – Local Kubernetes development with no stress

#6
post #4

is there anything working with helm in the similar way ?

There are at least two options that work with helm, google's skaffold (https://github.com/GoogleContainerTools/skaffold) and microsoft's draft (https://github.com/Azure/draft). The former supports helm along with kustomize and just plain old kubectl yaml files, draft seems to be tied to helm.

Personally I have used skaffold with success, and draft paniced on me so I stopped playing with it.

Re: Tilt – Local Kubernetes development with no stress

#7

My biggest problem with local k8s dev is building containers. I’m on macOS. Does this solution address that?

Is the problem with building containers that you don't have a Dockerfile and you don't want to spend time making one?

Draft does that pretty well with Draftpacks, in my experience if there is a Draftpack for what you're using then the Dockerfile that draft spits out will get you pretty close to a workable container image with basically no effort, or sometimes even all the way there.

I'm trying to understand what you mean that building containers is a problem. Is it the procedural act of actually building and rebuilding the container that is the problem? (Draft handles that too...)

Edit: According to the Tilt tutorial, yes, tilt will build your containers. Eg: https://docs.tilt.build/first_config.html

Re: Tilt – Local Kubernetes development with no stress

#9
post #2

Uuuuh not using YAML. Controversial. (in the docker/k8s ecosphere, where YAML seems ubiquitous) I don't love YAML though I am not sure Starlark looks any more readable. YACL => Yet another config language...?

This would be a stopper for me simply because all k8s config my team does is in yaml
Post reply on HN