GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
@@ -90,6 +90,13 @@ From now on charts located in this repository can be deployed by using the `--ch
## docker init
*`--docker-config`: sets the content of the file `~/.docker/config.json` which is used by docker to authenticate to the registry. This can contain multiple registry-servers and there credentials. Which registry is used depends on the image name.
*`--cluster-url`: sets the url to the kube-apiserver. This URL is provided by the k8s-admin.
*`--certificate-authority`: sets the certificate-authority certificate as base64-encoded string. This string is provided by the k8s-admin
*`--token`: sets the bearer token of the service-account as bas64-encoded string. This string is provided by the k8s-admin.
*`--namespace`: sets the k8s-namespace where the deployment is located. This string is provided by the k8s-admin.
*`--service-account`: this is the name of the service-account, that is used to perform the deployment.
*`--reset`: this ignores eventually existing config-folders of docker, helm and kubectl and removes them.
## docker build
...
...
@@ -98,16 +105,7 @@ From now on charts located in this repository can be deployed by using the `--ch
*`--output`: sets the filepath to the file where the built image is saved. If omitted the image is not saved to a file. Also the script trys to import an eventually existing file prior to building in order to make usage of its layers as build-cache.
*`--build-context`: sets the build-context for `docker build` to a custom path. If omitted the path where the command is invoked is used.
*`--reset`: this ignores eventually existing config-folders of docker, helm and kubectl and removes them.
## docker init
*`--docker-config`: sets the content of the file `~/.docker/config.json` which is used by docker to authenticate to the registry. This can contain multiple registry-servers and there credentials. Which registry is used depends on the image name.
*`--cluster-url`: sets the url to the kube-apiserver. This URL is provided by the k8s-admin.
*`--certificate-authority`: sets the certificate-authority certificate as base64-encoded string. This string is provided by the k8s-admin
*`--token`: sets the bearer token of the service-account as bas64-encoded string. This string is provided by the k8s-admin.
*`--namespace`: sets the k8s-namespace where the deployment is located. This string is provided by the k8s-admin.
*`--service-account`: this is the name of the service-account, that is used to perform the deployment.
*`--reset`: this ignores eventually existing config-folders of docker, helm and kubectl and removes them.
*`--image-name`: sets the image name in the local docker-registry. Can be useful for following builds to build upon existing builds
## docker publish
...
...
@@ -116,6 +114,7 @@ From now on charts located in this repository can be deployed by using the `--ch
*`--name`: sets the name of the image. If you do not wish to publish to [Docker-Hub], you have to specify a server, e.g. `registry.example.com/my-image`. **Be aware that you need to provide credentials in your docker-config if the registry requires authentication.
*`--tags`: sets the tags of the image. Provide multiple `--tag`-options if you wish to tag an image with multiple tags.
*`--reset`: this ignores eventually existing config-folders of docker, helm and kubectl and removes them.
*`--image-name`: specifys the image name in the local docker-registry to publish