Need to support not clobbering unneeded services when two repos deploy to the same namespace

[tobiasmcnulty]

Possibly by prefixing all resources with a project or app name of some sort...

[dpoirier]

I've been generating namespace names that contain both the project name and the deploy environment, e.g. "inddex-staging", thinking it would avoid that problem.

[tobiasmcnulty]

That is a good strategy. In this case I mean two separate frontend and API pods for the same environment, which I was thinking would make sense to deploy to the same namespace. They share the same domain and nginx ingress master. Separate namespaces might work too, but then we'd need a way to create the nginx master only once.

…

On Sat, Nov 16, 2019, 2:17 PM Dan Poirier ***@***.***> wrote: I've been generating namespace names that contain both the project name and the deploy environment, e.g. "inddex-staging", thinking it would avoid that problem. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=AABHDBCGCH4BPSNMXAQNOLLQUBBLTA5CNFSM4JN77IF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEHYQAA#issuecomment-554665984>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABHDBECB7VNGZ6AENEWDDDQUBBLTANCNFSM4JN77IFQ> .

[copelco]

We override k8_templates in ratom_web and let the backend repo handle the other services.