DevFW-CICD/argocd-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Allow TLS configuration for Ingress (#119)

Browse source
This commit is contained in:
leoxiongideahq 2019-09-24 09:58:42 +12:00 • committed by Alex Collins
parent 480c730725
commit 3fce11cdc2
3 changed files with 11 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

1
charts/argo-cd/README.md
View file

@ -59,6 +59,7 @@ $ helm install --name my-release argo/argo-cd
| ingress.additionalHosts | list | `[]` | Ingress additional hosts |
| ingress.annotations | object | `{}` | Annotations for ingress object, set `nginx.ingress.kubernetes.io/force-ssl-redirect: "true"` and `nginx.ingress.kubernetes.io/ssl-passthrough: "true"` if serving GRPC and HTTPS on the same ingress |
| ingress.enabled | bool | `false` | Enable ingress |
| ingress.tls | object | `{}` | Ingress TLS configuration |
| rbac.policyCsv | string | `nil` | RBAC policy in CSV, see [values.yaml](./values.yaml) for format |
| rbac.policyDefault | string | `nil` | The default role Argo CD will fall back to, when authorizing API requests, ie: `role:readonly` |
| rbac.scopes | string | `nil` | Scopes controls which OIDC scopes to examine during rbac enforcement (in addition to `sub` scope). ie: `[groups]` |