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
Can we update the Traefik nodeport chart to not use host port 9100 for it's metrics? This clashes with the kube-prometheus stack's node-exporter which also uses host port 9100.
As Traefik is a default marketplace option it'd be good to get this changed so people can install kube-prometheus straight onto their clusters.
k get ds traefik -o json | jq -r '.spec.template.spec.containers[0].ports[0]'
{
"containerPort": 9100,
"hostPort": 9100,
"name": "metrics",
"protocol": "TCP"
}
The text was updated successfully, but these errors were encountered:
This issue is a:
If the issue concerns an existing Marketplace application, please tag the maintainer of the application (found in
manifest.yaml
) below:@saiyam1814
Enhancement suggestions / feature requests
Can we update the Traefik nodeport chart to not use host port 9100 for it's metrics? This clashes with the kube-prometheus stack's node-exporter which also uses host port 9100.
As Traefik is a default marketplace option it'd be good to get this changed so people can install kube-prometheus straight onto their clusters.
The text was updated successfully, but these errors were encountered: