Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

PodMonitor using incorrect port name #601

Closed
pragmaticivan opened this issue Jan 27, 2024 · 0 comments · Fixed by #602
Closed

PodMonitor using incorrect port name #601

pragmaticivan opened this issue Jan 27, 2024 · 0 comments · Fixed by #602
Labels
bug Something isn't working

Comments

@pragmaticivan
Copy link
Contributor

A clear and concise description of what the bug is.

Expected Behavior

PodMonitor is able to scrape metrics from the operator.

Actual Behavior

Not being able to scrape because port name is incorrect.

Steps to Reproduce the Problem

  1. Just install using PodMonitor instead of ServiceMonitor

Specifications

  • KEDA Version: latest
  • Platform & Version: latest
  • Kubernetes Version: k8s 1.25
  • Scaler(s): Operating
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant