-
Notifications
You must be signed in to change notification settings - Fork 6
Do not create/update ServiceMonitor without verifying BasicAuth secrets #228
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
Conversation
|
This fix can also be delivered (or re-delivered) into RCO once application-stacks/runtime-component-operator#414 (Share controller code further) is merged, and then this WLO PR can update its controller code to call RCO utils. That way, the basicAuth fix can be applied to RCO and all extending operators rather than just WLO alone. |
|
Looks good to me for basicAuth. However, we might want to expand this check for other secret types. There are few supported by Prometheus (oauth2, authorization, bearerTokenSecret) |
- Validate Prometheus monitoring Secrets and ConfigMaps by breaking out of the reconcile loop if they do not exist. - Prevent validation of Secrets/ConfigMaps if the KeySelector's Optional parameter is set to true.
|
@arturdzm please review the updates when you get a chance. Thanks |
|
Closing, because this change is replaced by PR #554 |
This change does not allow creation or the updating of the Service Monitor if BasicAuth secrets are specified in the WSLA instance but do not actually exist.