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

setting APIServerEndpointURL does not change the endpoint being scraped #41

Closed
gsanchezgavier opened this issue Nov 12, 2020 · 0 comments · Fixed by #42
Closed

setting APIServerEndpointURL does not change the endpoint being scraped #41

gsanchezgavier opened this issue Nov 12, 2020 · 0 comments · Fixed by #42
Assignees
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@gsanchezgavier
Copy link
Contributor

gsanchezgavier commented Nov 12, 2020

Description

When set API_SERVER_ENDPOINT_URL the integration is setting the unsecure endpoint and when scrapes the api-server start doing it with the default secure endpoint localhost:443 and if fails falls back to the endpoint set in API_SERVER_ENDPOINT_URL.
If the first attempt to scrape localhost:443 do not fail that endpoint response anything (it happend in openshift 4.6 CodeRady container) the fall back mechanism never get activated and the endpoint that has been set to scrape never gets scraped.

Expected Behavior

When i set API_SERVER_ENDPOINT_URL that endpoint gets scraped directly without having to go over a falling mechanism.

Troubleshooting or NR Diag results

Steps to Reproduce

set API_SERVER_ENDPOINT_URL and verbose mode logs, and search for the api-server running job, it shows that localhost:443 is being scraped at first place.

Your Environment

CodeREady Openshift 4.6

Additional context

@gsanchezgavier gsanchezgavier added the bug Categorizes issue or PR as related to a bug. label Nov 12, 2020
@gsanchezgavier gsanchezgavier self-assigned this Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant