Skip to content

Provide separate namespaces for each project environment

What does this MR do?

Includes (and depends on) https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30551

Kubernetes deployments on new clusters will now have a separate namespace per project environment, instead of sharing a single namespace for the project. Namespaces are of the form <project-slug>-<project-id>-<environment-slug>.

Behaviour of existing clusters is unchanged.

All new functionality is controlled by the :kubernetes_namespace_per_environment feature flag, which is safe to enable/disable at any time.

Remaining questions:

  • Currently the feature flag defaults to disabled. Do we want it enabled by default instead? edit: Updated to be enabled by default.

Couple of extra notes:

TODO:

  • Docs
  • QA notes/screenshots

Does this MR meet the acceptance criteria?

Conformity

Performance and testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • [-] Label as security and @ mention @gitlab-com/gl-security/appsec
  • [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • [-] Security reports checked/validated by a reviewer from the AppSec team

#52494 (closed) #62666 (moved) #62667 (moved)

Edited by 🤖 GitLab Bot 🤖

Merge request reports

Loading