From 4bdc238fd5623ead91b258069d3ad6a2cf34b131 Mon Sep 17 00:00:00 2001 From: hc-github-team-secure-vault-core <82990506+hc-github-team-secure-vault-core@users.noreply.github.com> Date: Fri, 4 Feb 2022 01:48:48 -0500 Subject: [PATCH] backport of commit f852919af80a38a1fcc93fcef265acd86939a0ab (#13899) This pull request was automerged via backport-assistant --- .../docs/platform/k8s/helm/configuration.mdx | 22 +++++-------------- 1 file changed, 5 insertions(+), 17 deletions(-) diff --git a/website/content/docs/platform/k8s/helm/configuration.mdx b/website/content/docs/platform/k8s/helm/configuration.mdx index 50c32d7c54ad..68528398c770 100644 --- a/website/content/docs/platform/k8s/helm/configuration.mdx +++ b/website/content/docs/platform/k8s/helm/configuration.mdx @@ -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. @@ -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).