You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug a clear and concise description of what the bug is.
Hello, i've been banging my head for 2 hours straight and im unable to configure oauth for authenticating to alertmanager. The alertingEndpoints doesnt follow the official documentation and its really confusing . For example tlsConfig is translated to tls_config when the configuration file is rendered. These are some of the values i tried but none of them worked.
It seems the operator doesnt support the oauth2 option in the alertingEndpoints block, i used AdditionalAlertManagerConfigs to make it work, but can i disable the default endpoint that is created ?
Describe the bug a clear and concise description of what the bug is.
Hello, i've been banging my head for 2 hours straight and im unable to configure oauth for authenticating to alertmanager. The alertingEndpoints doesnt follow the official documentation and its really confusing . For example tlsConfig is translated to tls_config when the configuration file is rendered. These are some of the values i tried but none of them worked.
What's your helm version?
v3.17.0
What's your kubectl version?
v1.32.0
Which chart?
kube-prometheus-stack
What's the chart version?
68.2.0
What happened?
No response
What you expected to happen?
No response
How to reproduce it?
No response
Enter the changed values of values.yaml?
No response
Enter the command that you execute and failing/misfunctioning.
.
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: