IngressMonitorController
IngressMonitorController copied to clipboard
Add support for basic auth (uptimerobot.com)
uptimerobot.com supports adding basic auth (http_username & http_password) to monitors. It would be nice, if IngressMonitorController could set those settings via related Ingress annotations/secrets.
This also applies to Pingdom!
I've submitted a PR to bring this to Pingdom via an annotation and OS env (mounted secret); https://github.com/stakater/IngressMonitorController/pull/154
I've submitted a PR implementation for Statuscake #170
@xanonid @SinFulNard @DhiaTN why not having an annotation pointing to a secret for the credentials? this way you dont need to mount the secret into the deployment/pod for the get.env
@grebois - I didn't have the thought at the time (or experience to achieve that). So went with what I could think of.
I agree, its likely a better method of exposing the secret.
@SinFulNard are you at kubecon this next week? if you are lets talk about it f2f
Hi @grebois, me and @waseem-h will be there at KubeCon. We'd be happy to meet if you want to discuss something or just say Hi!
Definitely, let's catch up, are you already in Barcelona? whazatpp me +49 152 0249 6483
@hazim1093 @waseem-h @SinFulNard please leave this open for a bit longer I will work on a PR together with @DhiaTN to refactor this functionality, including https://github.com/stakater/IngressMonitorController/issues/182 and https://github.com/stakater/IngressMonitorController/issues/183
Definitely, let's catch up, are you already in Barcelona? whazatpp me +49 152 0249 6483
Hi, Sorry I didn't get notification for the comment, just saw :(
@grebois will you continue on this one?
@rasheedamir not for the moment, but I would like to keep it open.
ok sure! @grebois
This issue is stale because it has been open for 60 days with no activity.
This issue was closed because it has been inactive for 30 days since being marked as stale.
Reopening issues that inadvertently were closed as stale