which means the workspaces Team UI shows links that don't go anywhere which is confusing.
Generally we tend to create environments eagerly - then lazily create the actual underlying Namespace/Project as part of the CD Pipeline.
If a namespace is defined in the fabric8-environments ConfigMap, but it doesn't yet exist we should render that differently in the Team row on the workspaces page; to show that the namespace hasn't yet been created (maybe even have a Create button to create it (*).
BTW when creating namespaces; on OpenShift we need to use the ProjectRequests REST API (like Project) as this also adds the necessary RoleBindings so that you can use DeploymentConfigs. Creating a kubernetes Namespace tends to break DeploymentConfig
which means the workspaces Team UI shows links that don't go anywhere which is confusing.
Generally we tend to create environments eagerly - then lazily create the actual underlying Namespace/Project as part of the CD Pipeline.
If a namespace is defined in the
fabric8-environments
ConfigMap, but it doesn't yet exist we should render that differently in the Team row on the workspaces page; to show that the namespace hasn't yet been created (maybe even have aCreate
button to create it (*).BTW when creating namespaces; on OpenShift we need to use the ProjectRequests REST API (like Project) as this also adds the necessary RoleBindings so that you can use DeploymentConfigs. Creating a kubernetes Namespace tends to break DeploymentConfig