-
Notifications
You must be signed in to change notification settings - Fork 4
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(GPX-669):Multena: Add TLS support for datasources #382
Conversation
Lucostus
commented
Jul 13, 2023
- adapted to new config structure
- mount tls-secrets to the right location
- added kyverno policies to copy the tls secret from the appropriate namespaces
# Conflicts: # infra/gp-multena/Chart.yaml # infra/gp-multena/templates/system-datasources.yaml # infra/gp-multena/values.yaml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lass uns vielleicht über die tls-secrets und die k8s resources nochmal kurz quatschen.
@@ -87,6 +95,16 @@ spec: | |||
secret: | |||
secretName: {{ include "gp-multena.secretName" . }} | |||
{{- end }} | |||
{{- if eq .Values.tlsCopy.loki.enabled true }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bin mir nicht sicher, ob wir das mounting des secrets an das kopieren koppeln wollen.
kann ja sein, dass der proxy verwendet werden möchte, ohne kyverno am cluster zu haben und die:der anwender:in das zertifikat manuell überspielt, oder?
secret: | ||
secretName: {{ .Values.tlsCopy.loki.secretName }} | ||
{{- end }} | ||
{{- if eq .Values.tlsCopy.thanos.enabled true }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same wie oben