Commit 3d9ca2c7 authored by Nick Gaskill's avatar Nick Gaskill

Merge branch 'cleveland-master-patch-85726' into 'master'

Remove warning from custom namespaces

See merge request gitlab-org/gitlab!62127
parents 36e83099 b085be46
...@@ -351,16 +351,17 @@ You can customize the deployment namespace in a few ways: ...@@ -351,16 +351,17 @@ You can customize the deployment namespace in a few ways:
When you customize the namespace, existing environments remain linked to their current When you customize the namespace, existing environments remain linked to their current
namespaces until you [clear the cluster cache](#clearing-the-cluster-cache). namespaces until you [clear the cluster cache](#clearing-the-cluster-cache).
WARNING: #### Protecting credentials
By default, anyone who can create a deployment job can access any CI/CD variable in By default, anyone who can create a deployment job can access any CI/CD variable in
an environment's deployment job. This includes `KUBECONFIG`, which gives access to an environment's deployment job. This includes `KUBECONFIG`, which gives access to
any secret available to the associated service account in your cluster. any secret available to the associated service account in your cluster.
To keep your production credentials safe, consider using To keep your production credentials safe, consider using
[protected environments](../../../ci/environments/protected_environments.md), [protected environments](../../../ci/environments/protected_environments.md),
combined with either combined with *one* of the following:
- a GitLab-managed cluster and namespace per environment, - A GitLab-managed cluster and namespace per environment.
- *or*, an environment-scoped cluster per protected environment. The same cluster - An environment-scoped cluster per protected environment. The same cluster
can be added multiple times with multiple restricted service accounts. can be added multiple times with multiple restricted service accounts.
### Integrations ### Integrations
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment