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
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.
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
The text was updated successfully, but these errors were encountered:
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 endpointlocalhost:443
and if fails falls back to the endpoint set inAPI_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 theapi-server
running job, it shows that localhost:443 is being scraped at first place.Your Environment
CodeREady Openshift 4.6
Additional context
The text was updated successfully, but these errors were encountered: