Environment

• YugabyteDB Anywhere - all versions prior including 2.16.x

Issue

A recent Platform change allows users to specify a Kubernetes namespace in the region/zone configuration of the Kubernetes provider. This (optional) setting causes the Platform to deploy the Universe to that Kubernetes namespace (as opposed to automatically generating a namespace for the Universe).

However, currently, the platform can only deploy up to one Universe into the same namespace. This means that the provider + zone (with a namespace specified) can only be used to deploy up to one Universe. Attempts to deploy multiple Universes results in the following error:

Universe <name> already exists with provider <name>. Only one universe can be created with providers having KUBENAMESPACE set in the AZ config.

To resolve this issue, recommend advising customers to NOT specify the namespace in the provider configuration. This setting is optional and only needed for environments where the platform is unable to automatically create namespaces in the kubernetes cluster.

Please note - From 2.18.x, we now allow creating multiple universes in the same namespace.

Reference:

• https://github.com/yugabyte/yugabyte-db/issues/6551
• https://github.com/yugabyte/yugabyte-db/commit/ab0adaad658dc68a837aa8e6d8322d084e056914