Tanka should manage the namespace resource

[Duologic]

In the current setup, one needs to create the namespace manually or with k.core.v1.namepace. However, in line with letting Tanka set the namespace on a resource at runtime (based on the environment), it should also create and own a namespace if it doesn't exist already.

In this way, we completely mitigate the need of defining a namespace resource in Jsonnet and we wouldn't need a manual action to get one.

WDYT?

[issue-label-bot]

Issue-Label Bot is automatically applying the label kind/feature to this issue, with a confidence of 0.79. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[ghostsquad]

What if a namespace is part of the defined set of resources? I typically do this because I include labels and annotations to my namespaces.

Tanka could benefit from a concept of resource deploy ordering? Maybe that should be a separate issue?

[sh0rez]

@ghostsquad Tanka already sorts resources by dependency (namespaces + crd's first, etc).

This is probably about having the environment implicitely include it's default namespace, so you don't need to add it manually

[Duologic]

Exactly, if a namespace is created and managed in the jsonnet code, tanka should not interfere (also because of backwards compat).

[ghostsquad]

@ghostsquad Tanka already sorts resources by dependency (namespaces + crd's first, etc).

@sh0rez is it possible to manipulate that ordering?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ghostsquad]

Not stale

[sh0rez]

This has not come up in recent discussions, namespace handling appears to work just fine. Closing this issue.

Feel free to open another issue if urgent action becomes needed