Hugo ShakaandPaul Gottschling 920495c6d7 helm: allow custom CA in teleport-cluster without custom certs (#16325) ...

Provides a solution for #9298

This removes an unnecessary limitation of the Helm chart: `.Values.tls.existingCASecretName` can now be used without `.Values.tls.existingSecretName`. This allows users to trust their own CAs without building custom images.

Context:
- go's x509 library supports loading system certs based on the SSL_CERTS_FILE environment variable
- we are already using this in the chart to trust private CAs (teleport proxy needs to trust its own certs to start)
- users might want to trust custom CAs to
  - speak with a S3 backend (minio)
  - validate upstream app certs (unlike DB access you can't trust certs per-application)
  - trust another cluster
  - call an OIDC provider
- teleport-kube-agent chart already has the feature

Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>

2022-09-16 15:53:35 +00:00

..

teleport-cluster

helm: allow custom CA in teleport-cluster without custom certs (#16325)

2022-09-16 15:53:35 +00:00

teleport-kube-agent

Linting adjustment for comment-space complaint (#13280)

2022-09-15 19:05:38 +00:00

.lint-config.yaml

Added log configuration to teleport-cluster chart.

2021-12-21 21:50:58 -08:00

CONTRIBUTING.md

feat(helm): expose securityContext as a value (#13016)

2022-06-08 02:31:51 +00:00

index.html

Add link to Teleport Changelog in helm chart repository site. (#8734)

2021-10-26 17:43:32 -07:00