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(GPX-669):Multena: Add TLS support for datasources #382

Merged
merged 16 commits into from
Jul 19, 2023

Conversation

Lucostus
Copy link
Contributor

  • adapted to new config structure
  • mount tls-secrets to the right location
  • added kyverno policies to copy the tls secret from the appropriate namespaces

@Lucostus Lucostus self-assigned this Jul 13, 2023
@Lucostus Lucostus requested review from fhochleitner and removed request for fhochleitner July 17, 2023 06:56
Copy link
Contributor

@fhochleitner fhochleitner left a 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 }}
Copy link
Contributor

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 }}
Copy link
Contributor

Choose a reason for hiding this comment

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

same wie oben

@Lucostus Lucostus merged commit 68ab468 into develop Jul 19, 2023
5 checks passed
@Lucostus Lucostus deleted the feature/GPX-669 branch July 19, 2023 12:07
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.

2 participants