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
In case secret contains some invalid URL it will lead to alertmanager being unable to start and enter CrashLoopBackoff quite easily.
It would be great if operator would validate that content of key in secret is valid URL and would not apply this change to alertmanager, but write an error in log/status field for created resource.
The text was updated successfully, but these errors were encountered:
Currently, in case receiver is configured via VMAlertmanagerConfig it uses reference to secret to pull slack URL:
In case secret contains some invalid URL it will lead to alertmanager being unable to start and enter
CrashLoopBackoff
quite easily.It would be great if operator would validate that content of
key
in secret is valid URL and would not apply this change to alertmanager, but write an error in log/status field for created resource.The text was updated successfully, but these errors were encountered: