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
When enabling TLS (in my case using requestAutoCert), then the operator should update scrape target in the scrape config to use the correct scheme (http -> https) and correct port (80 -> 443).
Current Behavior
The config is not being updated if it exists. Deleting the config will eventually resolve the issue as the operator recreates the secret with the correct contents.
seems to check that the secret exists and that it contains a scrape config, but it doesn't seem to compare the config contents with what is expected.
Steps to Reproduce (for bugs)
Setup a new tenant without TLS and with promtheusOperator enabled
Enable TLS
Context
I enabled TLS, requestAutoCert specifically, while setting up KES, which made that a lot simpler. My ingress controller does TLS termination, that's why I previously didn't need TLS internally.
The text was updated successfully, but these errors were encountered:
Expected Behavior
When enabling TLS (in my case using
requestAutoCert
), then the operator should update scrape target in the scrape config to use the correct scheme (http -> https) and correct port (80 -> 443).Current Behavior
The config is not being updated if it exists. Deleting the config will eventually resolve the issue as the operator recreates the secret with the correct contents.
Possible Solution
operator/pkg/controller/prometheus.go
Lines 105 to 132 in ea9299f
Steps to Reproduce (for bugs)
Context
I enabled TLS,
requestAutoCert
specifically, while setting up KES, which made that a lot simpler. My ingress controller does TLS termination, that's why I previously didn't need TLS internally.The text was updated successfully, but these errors were encountered: