Some ideas:

• kube-state-metrics
• metric-server

Today I have this hacked up with a list of namespaces -- but we'd want something with a compile-time check instead.

Use-cases

• global + appNamespace
• multiple app namespaces (e.g. operator + deployment)

This will end up being a refinement of 72fa403

Fundamentally we can either:

• Create "placeholder" environments to get reviews/approvals defined that way
• move the approval config back to the namespace -- this way an environment can "own" multiple namespaces

Either approach is safe as tanka already protects from N definitions of the same resource (e.g. namespace)

As of now there are some assumptions about labels existing on the namespace. This is an alright approach for now, but it feels like this should be something attached to the actual Environment object to handle configuration there.

This repo is based off of some older work (prior to helm being a thing) now that helm exists I want to extend this to enable the re-use of helm charts

It takes this example build from ~1.5s -> ~6s