Docs review for MR 25586
This commit is contained in:
parent
d119fd493f
commit
a66db7be8c
2 changed files with 16 additions and 19 deletions
|
@ -652,7 +652,7 @@ repo or by specifying a project variable:
|
|||
|
||||
### Custom Helm chart per environment **[PREMIUM]**
|
||||
|
||||
You can specify the use of a custom Helm chart per environment by scoping the environment variable
|
||||
You can specify the use of a custom Helm chart per environment by scoping the environment variable
|
||||
to the desired environment. See [Limiting environment scopes of variables](https://docs.gitlab.com/ee/ci/variables/#limiting-environment-scopes-of-variables-premium).
|
||||
|
||||
### Customizing `.gitlab-ci.yml`
|
||||
|
@ -1022,10 +1022,9 @@ planned for a subsequent release.
|
|||
buildpack](#custom-buildpacks).
|
||||
- Auto Test may fail because of a mismatch between testing frameworks. In this
|
||||
case, you may need to customize your `.gitlab-ci.yml` with your test commands.
|
||||
- Auto Deploy may fail if it is unable to create a Kubernetes namespace and
|
||||
service account for your project. See the
|
||||
[troubleshooting failed deployments](../../user/project/clusters/index.md#troubleshooting-failed-deployment-jobs)
|
||||
section to debug why these resources were not created.
|
||||
- Auto Deploy will fail if GitLab can not create a Kubernetes namespace and
|
||||
service account for your project. For help debugging this issue, see
|
||||
[Troubleshooting failed deployment jobs](../../user/project/clusters/index.md#troubleshooting-failed-deployment-jobs).
|
||||
|
||||
### Disable the banner instance wide
|
||||
|
||||
|
|
|
@ -548,25 +548,23 @@ service account of the cluster integration.
|
|||
### Troubleshooting failed deployment jobs
|
||||
|
||||
GitLab will create a namespace and service account specifically for your
|
||||
deployment jobs. These resources are created just before the deployment
|
||||
job starts. Sometimes there may be errors that cause their creation to fail.
|
||||
deployment jobs, immediately before the jobs starts.
|
||||
|
||||
In such instances, your job will fail with the message:
|
||||
However, sometimes GitLab can not create them. In such instances, your job will fail with the message:
|
||||
|
||||
```The job failed to complete prerequisite tasks```
|
||||
```text
|
||||
The job failed to complete prerequisite tasks
|
||||
```
|
||||
|
||||
You will need to check the [logs](../../../administration/logs.md) to debug
|
||||
why the namespace and service account creation failed.
|
||||
To find the cause of this error when creating a namespace and service account, check the [logs](../../../administration/logs.md#sidekiqlog).
|
||||
|
||||
A common reason for failure is that the token you gave GitLab did not have
|
||||
[`cluster-admin`](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles)
|
||||
privileges as GitLab expects.
|
||||
Common reasons for failure include:
|
||||
|
||||
Another common problem is caused by a missing `KUBECONFIG` or `KUBE_TOKEN`.
|
||||
To be passed to your job, it must have a matching
|
||||
[`environment:name`](../../../ci/environments.md#defining-environments). If
|
||||
your job has no `environment:name` set, it will not be passed the Kubernetes
|
||||
credentials.
|
||||
- The token you gave GitLab did not have [`cluster-admin`](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles)
|
||||
privileges required by GitLab.
|
||||
- Missing `KUBECONFIG` or `KUBE_TOKEN` variables. To be passed to your job, they must have a matching
|
||||
[`environment:name`](../../../ci/environments.md#defining-environments). If your job has no
|
||||
`environment:name` set, it will not be passed the Kubernetes credentials.
|
||||
|
||||
## Monitoring your Kubernetes cluster **[ULTIMATE]**
|
||||
|
||||
|
|
Loading…
Reference in a new issue