When specifying a deployment namespace with `tilt up --namespace <NAMESPACE>`, if `<NAMESPACE>` does not currently exist, create the namespace. about tilt HOT 4 OPEN

hmmm...i'm not sure we should do this.

The tilt --namespace flag is indented to map to kubectl --namespace. In kubectl, it sets the default namespace for API requests - https://pkg.go.dev/k8s.io/[email protected]/tools/clientcmd/api/v1#Context

kubectl --namespace=... apply does not auto-create the namespace.

Helm has a separate --create-namespace flag, which you can simulate in tilt as:

namespace_create(k8s_namespace())

from tilt.

@nicks Fair concerns. Regardless, I would make the case that this is a reasonable quality-of-life improvement. If tying it directly to the --namespace flag is undesirable, perhaps adding a separate tilt --create-namespace flag to be analogous to the underlying helm --create-namespace flag?

I would make the argument that the current reliance namespace_create(k8s_namespace()) is non-intuitive, and contrasts with the linked tilt feature announcement. The --namespace flag being provided out of the box contrasts with the need to load a separate extension for namespace_create(...). At minimum, if specifying the --namespace flag and the namespace does not exist, I would expect to see the initial tilt up fail immediately.

from tilt.

ya, i guess we'd accept a --create-namespace flag that mirrors the helm flag behavior

from tilt.

To make sure we're on the same page-- I'm thinking that this would be a tilt flag on the up command. For instance, tilt up --create-namespace. The flag would be meaningless (and provide an associated error) if not paired with the --namespace flag, and it would result in the namespace being created prior to the actual contents of the Tiltfile being processed.

from tilt.