| ... | ... | @@ -24,9 +24,11 @@ You can give as much information as possible to the team for creation: |
|
|
|
|
|
|
|
### Deploy tokens
|
|
|
|
|
|
|
|
In your gitlab project, under `Settings/Repository/Deploy tokens` you can create tokens to deal with access to packages, your repository, and registry images.
|
|
|
|
|
|
|
|
1. Create your token
|
|
|
|
* name: kubernetes
|
|
|
|
* scopes: read_registry
|
|
|
|
2. Add the token to your Variables `Settings/CI/CD/Variables` and name it `DEPLOY_TOKEN` for instance |
|
|
\ No newline at end of file |
|
|
|
> You can name variables the way you want, of course.
|
|
|
|
|
|
|
|
1. Create your token (`Settings/Repository/Deploy tokens`)
|
|
|
|
* **name**: kubernetes
|
|
|
|
* **scopes**: read_registry
|
|
|
|
2. Add the new informations to your Variables (`Settings/CI/CD/Variables`)
|
|
|
|
* Add the username (by default `gitlab+deploy-token-xx`) and name it `DEPLOY_USER`
|
|
|
|
* Add the token and name it `DEPLOY_TOKEN` |
|
|
\ No newline at end of file |
