-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Prometheus autodiscovery not using HTTPS #16751
Comments
Hello @Mstrodl 👋 Thanks for opening this issue. Could you please open a support ticket for this? This will be easier to track on our side and to get further information 🙁 Thank you! |
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: If you have a feature request, you should contact support so the request can be properly tracked.
Output of the info page
agent-status.txt
Additional environment details (Operating System, Cloud provider, etc):
Using helm chart on OKD4:
relevant
values.yaml
snippet:Steps to reproduce the issue:
Describe the results you received:
400 errors from the server ("An http request was sent to an https port"):
Describe the results you expected:
The agent should obey the
scheme
annotationAdditional information you deem important (e.g. issue happens only occasionally):
We only started seeing this recently. I think the upgrade to OKD4 4.13.0 is to blame?
The text was updated successfully, but these errors were encountered: