-
Notifications
You must be signed in to change notification settings - Fork 605
Helm: Simplified TLS configuration #11776
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
base: main
Are you sure you want to change the base?
Conversation
…ovements # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
Mindful that I haven't got any docs in this PR yet - definitely will add some examples of how to use the new values that are available to people. Possibly as an update to [Securing Communications with TLS].(https://grafana.com/docs/mimir/latest/manage/secure/securing-communications-with-tls/) Just holding off on that temporarily until the team has had a chance to review, in case any substantial changes are needed. |
What this PR does
This PR adds a new tls key to the Helm values, and updated templates to simplify the configuration of TLS between Mimir services.
This change is for traffic within the Mimir/GEM cluster, including Memcached (i.e. not how the cluster is exposed to clients).
Currently, enabling encryption in transit within the cluster requires a lot of configuration changes. Below is an example of some of the changes required for a GEM cluster (there are other values, but I've kept only the settings required to enable TLS).
Current values required for enabling TLS
With the changes to templates and new default values provided in this PR, the values file is much simpler and becomes (for example).
Proposed values required for enabling TLS
Another comparison is available in the 2 CI tests:
enterprise-https-values.yaml
(original) andenterprise-https-simple-values.yaml
(using the new tls object).Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
. If changelog entry is not needed, please add thechangelog-not-needed
label to the PR.about-versioning.md
updated with experimental features.