Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Traefik-v2-nodeport metrics hostport #356

Open
1 of 3 tasks
jakeloxton opened this issue Nov 24, 2022 · 2 comments
Open
1 of 3 tasks

Traefik-v2-nodeport metrics hostport #356

jakeloxton opened this issue Nov 24, 2022 · 2 comments

Comments

@jakeloxton
Copy link

This issue is a:

  • Bug Report
  • Enhancement suggestion
  • Feature request

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.

k get ds traefik -o json | jq -r '.spec.template.spec.containers[0].ports[0]'
{
  "containerPort": 9100,
  "hostPort": 9100,
  "name": "metrics",
  "protocol": "TCP"
}
@DMajrekar
Copy link
Contributor

@jakeloxton
Copy link
Author

ports.metrics.port is the key to change.

It's actually mentioned in the official Helm chart

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants