We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What happened: When we tried to deploy kube-prometheus-stack by using PipeCD, plan preview failed like this↓
kube-prometheus-stack
What you expected to happen:
We want to succeed to do a plan preview.
How to reproduce it:
values.yaml
alertmanager: ... config: receivers: - name: 'pagerduty-notifications' pagerduty_configs: - service_key: {{.encryptedSecrets.key}} templateFiles: template_2.tmpl: |- {{ define "slack.custom.v2.text" }} {{ range .Alerts }} {{ if eq .Status "firing" }}{{ .Annotations.description }}{{else}}{{ .Annotations.resolved_description }}{{end}} {{ end }} {{ end }} {{ define "slack.custom.v2.title" }} [{{ .Status | toUpper }}{{ if eq .Status "firing" }}:{{ .Alerts.Firing | len }}{{ end }} {{ .GroupLabels.severity }}] {{ .GroupLabels.alertname }} {{ end }}
Environment:
piped
control-plane
The text was updated successfully, but these errors were encountered:
This happens because the custom alert template is parsed as Golang's text/template when parsing the encryptionSecret (from PipeCD).
Sorry, something went wrong.
Workaround:
.encryptedSecrets.key
{{``}}
No branches or pull requests
What happened:
When we tried to deploy
kube-prometheus-stack
by using PipeCD, plan preview failed like this↓What you expected to happen:
We want to succeed to do a plan preview.
How to reproduce it:
kube-prometheus-stack
values.yaml
Environment:
piped
version:control-plane
version:The text was updated successfully, but these errors were encountered: