Closed vyasgun closed 5 months ago
Can you put more info in the commit logs why it was not working without this PR and what this PR adds to make it work?
Thanks @praveenkumar. Just added more info to the commit log.
@vyasgun: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/e2e-crc | ee48b763ed33cccb3f4a4a751feb28a0fa7a00b6 | link | true | /test e2e-crc |
ci/prow/security | d4f7279eb0ef0074b16e7e642a69176c0f3942bd | link | false | /test security |
ci/prow/integration-crc | d4f7279eb0ef0074b16e7e642a69176c0f3942bd | link | true | /test integration-crc |
Full PR test history. Your PR dashboard.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gbraad
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Fixes: Issue #4124
Relates to: Issue #4177 (Maybe)
Solution/Idea
This is a workaround to explicitly set the
ingressPortNumber
in theIssuer
field when requesting token. By default, the OpenShift library uses the URL from/.well-known/oauth-authorization-server
without including the custom port set by the user on CRC. This omission causes errors when writing new contexts to kubeconfig, as the token request fails due to the missing port number. Since users configure this custom port for their CRC instance, this commit ensures the issuer field includes the ingress-https-port before making the token request.Proposed changes
List main as well as consequential changes you introduced or had to introduce.
Testing
crc config set ingress-https-port 7443
crc setup
crc start