You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating service instances through consumer UI, we should enforce that the service instance name adhere to following convention: alphanumeric or hyphen with the initial letter not being an hyphen. These are the constraints that are defined by Kubernetes for defining namespaces. The reason we want to set these constraints for defining the service instance names as well is because, KubePlus will create namespace with the service name and then deploy the service Helm chart in that namespace. So we want to make sure that the service name adheres to the naming policies for Kubernetes Namespaces.
The text was updated successfully, but these errors were encountered:
When creating service instances through consumer UI, we should enforce that the service instance name adhere to following convention: alphanumeric or hyphen with the initial letter not being an hyphen. These are the constraints that are defined by Kubernetes for defining namespaces. The reason we want to set these constraints for defining the service instance names as well is because, KubePlus will create namespace with the service name and then deploy the service Helm chart in that namespace. So we want to make sure that the service name adheres to the naming policies for Kubernetes Namespaces.
The text was updated successfully, but these errors were encountered: