Project and namespace naming issue when deploying a service into the same cluster as Kargo

[oscr]

Checklist

• I've searched the issue queue to verify this is not a duplicate feature request.
  * [ ] I've pasted the output of kargo version, if applicable.
  * [ ] I've pasted logs, if applicable.

Proposed Feature

Either:

• Add a Project "display name" which is used in the Kargo UI instead of Project name if it is set.
• Add the option to name the Project namespace.
• Add the option to adopt a namespace with a different name than the Project.

Motivation

When creating a Project Kargo will create a matching namespace with the same name. It is also possible for a project to adopt an existing namespace. However adoption seems to require Project and namespace name to match.

But assume we want to deploy a service into the same cluster as Kargo itself is running in. For example cert-manager. If we call the Project cert-manager then both Kargo and cert-manager will try to create resources in the same namespace. This could be avoided by placing cert-manager in another namespace or e g calling the Project something like cert-manager-project. But it would be nice to just have a cert-manager project i Kargo.

Thank you team for your great work with Kargo!

Suggested Implementation

[remi-gelinas]

+1, I scope namespaces to kargo- for existing services, and it's just UI cruft to have the display name be prefixed as well. I'd love the ability to provide a display name separately.