Christopher Larivière

> I managed to get rid of the alerts. > > Used chart: https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack > > **chart config** > > ```yaml > kubeControllerManager: > endpoints: > - > service: >...

i followed https://microk8s.io/docs/external-lma omitting the --show-hidden-metrics-for-version (i didn't need it) i added the following kube-controler-manager: ``` --bind-address 0.0.0.0 --secure-port 10257 ``` for this i had to redeploy the kube-prometheus stack...

It appears that kube-scheduler and kube-controller-manager run on https now. https://microk8s.io/docs/services-and-ports#heading--auth you'll have to set it up so that the `serviceMonitors` ignore the ssl cert and use `https: true`

Also, pretty sure this issue can be closed

> i got something here that works for me. > > # Steps to enable controller-manager, scheduler and kube-proxy metrics in Prometheus > > ## Controller manager > Before prometheus...

imo, if I'm the only one having the issue this PR may not be worth. Although, I'm glad that you found a solution. I do believe that this would be...

Is there a chance this will be merged? 😊

Could it be you installed k8s 1.22? Im having issues with kubenav since upgrading, was wondering it it could be this For example: https://github.com/kubenav/kubenav/blob/master/src/components/resources/discoveryAndLoadbalancing/ingresses/IngressDetails.tsx#L69-L70 These paths no longer exist in...

> I'm experiencing the same behavior. For OPTIONS requests coming from origins which do not match the allowed-origins configured through `nginx.ingress.kubernetes.io/cors-allow-origin`, there are no returned CORS headers. This is resulting...

I will try to take a look at this when I have time Until then feel free to comment :)