feat(argo-rollouts): add dashboard (#798)
* feat(argo-rollouts): add dashboard deployment and service
credit: the implemention is inspired by the work from
Andrii Perenesenko <andrii.perenesenko@gmail.com>.
Signed-off-by: Hui Kang <hui.kang@salesforce.com>
* Apply suggestions from code review
Signed-off-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>
* Add components to selectlabels
Signed-off-by: Hui Kang <hui.kang@salesforce.com>
* Bump major version and add upgrading note
Signed-off-by: Hui Kang <hui.kang@salesforce.com>
* fix: Documentation on dashboard values, change annotations
Signed-off-by: Hui Kang <hui.kang@salesforce.com>
* feat: Enable dashboard during chart testing
Signed-off-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>
Co-authored-by: Hui Kang <hui.kang@salesforce.com>
Co-authored-by: Marco Kilchhofer <mkilchhofer@users.noreply.github.com>
This commit is contained in:
parent
879453808c
commit
3053af0500
12 changed files with 228 additions and 5 deletions
|
|
@ -25,6 +25,9 @@ $ helm repo add argo https://argoproj.github.io/argo-helm
|
|||
$ helm install my-release argo/argo-rollouts
|
||||
```
|
||||
|
||||
If dashboard is installed by `--set dashboard.enabled=true`, checkout the argo-rollouts dashboard by
|
||||
`kubectl port-forward service/argo-rollouts-dashboard 31000:3100` and pointing the browser to `localhost:31000`
|
||||
|
||||
## Chart Values
|
||||
|
||||
| Key | Type | Default | Description |
|
||||
|
|
@ -53,9 +56,30 @@ $ helm install my-release argo/argo-rollouts
|
|||
| 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 |
|
||||
| dashboard.enabled | bool | `false` | Deploy dashboard server |
|
||||
| dashboard.component | string | `"rollouts-dashboard"` | Value of label `app.kubernetes.io/component` |
|
||||
| dashboard.image.pullPolicy | string | `"IfNotPresent"` | Image pull policy |
|
||||
| dashboard.image.registry | string | `quay.io` | Registry to use |
|
||||
| dashboard.image.repository | string | `"argoproj/kubectl-argo-rollouts"` | Repository to use |
|
||||
| dashboard.image.tag | string | `""` | Overrides the image tag (default is the chart appVersion) |
|
||||
| dashboard.resources | object | `{}` | Resource limits and requests for the dashboard pods. |
|
||||
| dashboard.tolerations | list | `[]` | [Tolerations for use with node taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) |
|
||||
| dashboard.affinity | object | `{}` | [Assign custom affinity rules to the deployment](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/) |
|
||||
| dashboard.nodeSelector | object | `{}` | [Node selector](https://kubernetes.io/docs/user-guide/node-selection/) |
|
||||
| dashboard.podSecurityContext | object | `{"runAsNonRoot": true}` | Security Context to set on pod level |
|
||||
| dashboard.containerSecurityContext | object | `{}` | Security Context to set on container level |
|
||||
| dashboard.serviceAccount.create | bool | `true` | Specifies whether a dashboard service account should be created |
|
||||
| dashboard.serviceAccount.annotations | object | `{}` | Annotations to add to the dashboard service account |
|
||||
| dashboard.serviceAccount.name | string | `""` | The name of the dashboard service account to use. If not set and create is true, a name is generated using the fullname template |
|
||||
|
||||
## Upgrading
|
||||
|
||||
### To 2.0.0
|
||||
|
||||
* The argo-rollouts dashboard is added to the template and can be enabled by setting `dashboard.enabled=true`.
|
||||
* There is a breaking change where the selector label `app.kubernetes.io/component: {{ .Values.controller.component }}` is added to rollout's deployment and service in order to distinguish between the controller and the dashboard component.
|
||||
To upgrade an existing installation, please **add the `--force` parameter** to the `helm upgrade` command or **delete the Deployment and Service resource** before you upgrade. This is necessary because Deployment's label selector is immutable.
|
||||
|
||||
### 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.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue