* feat(argo-rollouts): Update manifests for v1.0.1 Signed-off-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com> * fix: add template function for labels Signed-off-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com> * fix: Apply changes from code review Signed-off-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com> Co-authored-by: Oliver Bähler <oliverbaehler@hotmail.com> |
||
---|---|---|
.. | ||
templates | ||
.helmignore | ||
Chart.yaml | ||
README.md | ||
values.yaml |
README.md
Argo Rollouts Chart
A Helm chart for Argo Rollouts, progressive delivery for Kubernetes.
Source code can be found here
Additional Information
This is a community maintained chart. This chart installs argo-rollouts, progressive delivery for Kubernetes.
The default installation is intended to be similar to the provided Argo Rollouts releases.
Prerequisites
- Kubernetes 1.7+
- Helm v3.0.0+
Installing the Chart
To install the chart with the release name my-release
:
$ helm repo add argo https://argoproj.github.io/argo-helm
$ helm install my-release argo/argo-rollouts
Chart Values
Key | Type | Default | Description |
---|---|---|---|
clusterInstall | bool | true |
false runs controller in namespaced mode (does not require cluster RBAC) |
controller.component | string | "rollouts-controller" |
Value of label app.kubernetes.io/component |
controller.image.pullPolicy | string | "IfNotPresent" |
Image pull policy |
controller.image.registry | string | quay.io |
Registry to use |
controller.image.repository | string | "argoproj/argo-rollouts" |
Repository to use |
controller.image.tag | string | "" |
Overrides the image tag (default is the chart appVersion) |
controller.resources | object | {} |
Resource limits and requests for the controller pods. |
controller.tolerations | list | [] |
Tolerations for use with node taints |
controller.affinity | object | {} |
Assign custom affinity rules to the deployment |
controller.nodeSelector | object | {} |
Node selector |
controller.metrics.serviceMonitor.enabled | bool | false |
Enable a prometheus ServiceMonitor |
controller.metrics.serviceMonitor.additionalAnnotations | object | {} |
Annotations to be added to the ServiceMonitor |
controller.metrics.serviceMonitor.additionalLabels | object | {} |
Labels to be added to the ServiceMonitor |
imagePullSecrets | list | [] |
Registry secret names as an array |
installCRDs | bool | true |
Install and upgrade CRDs |
crdAnnotations | object | {} |
Annotations to be added to all CRDs |
podAnnotations | object | {} |
Annotations to be added to the Rollout pods |
podLabels | object | {} |
Labels to be added to the Rollout pods |
serviceAccount.create | bool | true |
Specifies whether a service account should be created |
serviceAccount.annotations | object | {} |
Annotations to add to the service account |
serviceAccount.name | string | "" |
The name of the service account to use. If not set and create is true, a name is generated using the fullname template |
podSecurityContext | object | {"runAsNonRoot": true} |
Security Context to set on pod level |
containerSecurityContext | object | {} |
Security Context to set on container level |
Upgrading
To 1.0.0
- This is a breaking change which only supports Helm v3.0.0+ now. If you still use Helm v2, please consider upgrading because v2 is EOL since November 2020.
To migrate to Helm v3 please have a look at the Helm 2to3 Plugin. This tool will convert the existing ConfigMap used for Tiller to a Secret of typehelm.sh/release.v1
. quay.io
is the default registry now- We introduce a template function for the labels here to reduce code duplication. This also affects the Deployment
matchLabels
selector.
To upgrade an existing installation, please add the--force
parameter to thehelm upgrade
command or delete the Deployment resource before you upgrade. This is necessary because Deployment's label selector is immutable. - All resources are now prefixed with the template
"argo-rollouts.fullname"
. This enables the users to override resource names via thenameOverride
andfullnameOverride
parameters. - Breaking parameters update
securityContext
was renamed tocontainerSecurityContext
- Added
controller.image.registry
. Prior to this chart version you had to override the registry viacontroller.image.repository