Description
We are deploying ingressmonitorcontroller (using helm) on its own namespace, and having ingress(es) running on other namespaces. Some of them have basic-auth enabled (using https://kubernetes.github.io/ingress-nginx/examples/auth/basic/). The secrets therefore are managed with another helm chart and stored in other namespaces with different format (htaccess).
I tried setting up the pingdom authentication config with pingdom.monitor.stakater.com/basic-auth-user but it requires a lot of manual steps in our use case. Same as setting env via the use of .Values.ingressMonitorController.secrets.
How about having another annotation (pingdom.monitor.stakater.com/basic-auth-id for example), to specify an id in the ingress annotation, then in ingressMonitorController we can check for a setting (for example .Values.ingressMonitorController.basicAuth.id) that configure both username and password to be sent to pingdom instead? If it's ok then I can create a PR.
Activity