Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of docs/helm: fix duplicate ingress tls section into stable-website #13899

Merged
merged 1 commit into from
Feb 4, 2022
Merged

Backport of docs/helm: fix duplicate ingress tls section into stable-website #13899

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 5 additions & 17 deletions website/content/docs/platform/k8s/helm/configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -329,13 +329,14 @@ and consider if they're appropriate for your deployment.
number: use-annotation
```

- `tls` (`array: []`) - Configure the TLS portion of the Ingress spec.
- `tls` (`array: []`) - Configures the TLS portion of the [Ingress spec](https://kubernetes.io/docs/concepts/services-networking/ingress/#tls), where `hosts` is a list of the hosts defined in the Common Name of the TLS certificate, and `secretName` is the name of the Secret containing the required TLS files such as certificates and keys.

```yaml
tls:
- secretName: chart-example-tls
hosts:
- chart-example.local
- hosts:
- sslexample.foo.com
- sslexample.bar.com
secretName: testsecret-tls
```

- `hosts` - Values that configure the Ingress host rules.
Expand Down Expand Up @@ -366,19 +367,6 @@ and consider if they're appropriate for your deployment.

- `tls` (`dictionary: {termination: passthrough}`) - TLS config that will be passed directly to the route's TLS config, which can be used to configure other termination methods that terminate TLS at the router.

- `tls` - Values that configure the Ingress TLS rules.

- `hosts` (`array: []`): List of the hosts defined in the Common Name of the TLS Certificate.

- `secretName` (`string: null`): Name of the secret containing the required TLS files such as certificates and keys.

```yaml
hosts:
- sslexample.foo.com
- sslexample.bar.com
secretName: testsecret-tls
```

- `authDelegator` - Values that configure the Cluster Role Binding attached to the Vault service account.

- `enabled` (`boolean: true`) - When set to `true`, a Cluster Role Binding will be bound to the Vault service account. This Cluster Role Binding has the necessary privileges for Vault to use the [Kubernetes Auth Method](/docs/auth/kubernetes).
Expand Down