clarify "namespace doesn't exist"

[jpetazzo]

clarify "namespace doesn't exist"

[jpetazzo]

Not quite! On line 43, we show how to create a namespace, but this is not an exercise; i.e. we don't run it and we don't expect people to run it. It's just to give the command.

So on line 93, the namespace hasn't been created yet (we just point the config file to it); Helm will create it automatically though.

[bridgetkromhout]

Ah! Do you think we want to clarify on the slide that this isn't an exercise? I know it doesn't have the "exercise" label, but since it's working code, people may try to run it anyhow. Maybe it's worth clarifying the place the namespace gets created?

[jpetazzo]

I was relying on the fact that it's idempotent, and it doesn't hurt whether people run it or not.

Likewise, we give a few kubectl get (and other "read" commands) outside of exercise blocks.

But yes .. .Hmm..

Perhaps instead of "the namespace doesn't exist yet" this should say "this doesn't create the namespace" or something like that.

[bridgetkromhout]

Perhaps instead of "the namespace doesn't exist yet" this should say "this doesn't create the namespace" or something like that.

Right, like, we shouldn't assert that something doesn't exist when we gave a command that could create it. I'm imagining that if the namespace is being created by ✨magic ✨ elsewhere, we should clarify that has happened, when it's happening?

[jpetazzo]

The namespace is created automatically by Helm, and it is mentioned there:

https://github.com/jpetazzo/container.training/blob/master/slides/kube/namespaces.md#creating-namespaces

Do you think it needs to be clarified further?

[bridgetkromhout]

What we have on the slide currently says "if" and yes, that "if" does apply to us. What I think is unclear (and what I still don't fully understand) is exactly which helm command creates that specific "blue" namespace, and when. Like, we tell it to use a context - is it happening then? Without further research/reading, that's not obvious to me, so I also think it won't be obvious to workshop participants.

[jpetazzo]

As far as I understand, Helm will use the default kube configuration. Therefore, with our kube config set-context ... commands, we end up instructing Helm to use a specific namespace as well.

Then (still as far as I understand) Helm has some logic like "if you ask me to create a resource in a namespace that doesn't exist, I will create the namespace for you." As a result, helm install ... will create the namespace.

[bridgetkromhout]

Okay, that makes sense. I will ponder this a little more and see how it works in practice before I raise an issue for any possible re-wording.