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.
@@ -88,11 +88,26 @@ From now on charts located in this repository can be deployed by using the `--ch
# Advanced Configuration
## docker init
## docker build
*`--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.
*`--build-arg`: used to provide build-arguments do `docker build`-command. This is mainly used for `HTTP_PROXY`/`http_proxy`: When you specify `--build-arg HTTP_PROXY=...` the tool adds the build argument `--build-arg http_proxy=...` as well, so lower-case proxy-variables are provided automatically. Nevertheless can you use this option to provide your own build-arguments within the `Dockerfile`
*`--output`: sets the filepath to the file where the built image is saved. If omitted the image is not saved to a file
*`--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.
## docker publish
...
...
@@ -100,6 +115,7 @@ From now on charts located in this repository can be deployed by using the `--ch
*`--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.
*`--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.
## docker deploy
...
...
@@ -114,6 +130,7 @@ From now on charts located in this repository can be deployed by using the `--ch
*`--set`: overrides the values from `Values.yaml` in the helm-charts. Provide multiple `--set`-options if you want to provide multiple overrides.
*`--set-string`: overrides the values from `Values.yaml` in the helm-charts as string. Provide multiple `--set-string`-options if you want to provide multiple overrides.
*`--timeout`: sets the timeout for helm. defaults to `60` seconds.
*`--reset`: this ignores eventually existing config-folders of docker, helm and kubectl and removes them.
## docker undeploy
...
...
@@ -123,6 +140,7 @@ From now on charts located in this repository can be deployed by using the `--ch
*`--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. This string is provided by the k8s-admin
*`--name`: sets the name of the deployment.
*`--reset`: this ignores eventually existing config-folders of docker, helm and kubectl and removes them.
## docker add-repo
...
...
@@ -133,6 +151,7 @@ From now on charts located in this repository can be deployed by using the `--ch
*`--service-account`: this is the name of the service-account, that is used to perform the deployment. This string is provided by the k8s-admin
*`--name`: sets the name of the repo to add.
*`--repo-url`: sets the repository-url of the repo to add.
*`--reset`: this ignores eventually existing config-folders of docker, helm and kubectl and removes them.