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.

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

feat: set Istio gateway TLS from Kubernetes secret #982

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

JeffResc
Copy link
Member

@JeffResc JeffResc commented Nov 5, 2024

Description

Adds the ability to set Istio gateway TLS from Kubernetes secret

Related Issue

Fixes #976

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Other (security config, docs update, etc)

Checklist before merging

@JeffResc JeffResc marked this pull request as ready for review November 14, 2024 17:21
@JeffResc JeffResc requested a review from a team as a code owner November 14, 2024 17:21
Copy link
Contributor

@mjnagel mjnagel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM overall - two small comments.


#### Configuring TLS from a Secret

As an alternative to specifying individual certificate, key, and CA certificate values, you can set `tls.credentialName` in the gateway configuration. This field specifies the name of a Kubernetes secret containing the TLS certificate, key, and optional CA certificate for the gateway. When `tls.credentialName` is set, it will override `tls.cert`, `tls.key`, and `tls.cacert` values, simplifying the configuration by allowing a direct reference to a Kubernetes TLS secret.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nits on the docs:

  • might be good to explicitly call out the required fields in the existing secret if using that, or alternatively link to Istio docs on this (i.e. the section from here)
  • might also be good to explicitly call out the namespaces that these secrets should be in (iirc they need to be in the same namespace as the gateway)

src/istio/chart/templates/tls-cert.yaml Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow Istio Ingress TLS Certificate from Secret
2 participants