-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
management-network-access-oidc
-
Product / Portfolio Work
-
-
False
-
-
False
-
Not Selected
-
None
-
None
-
None
-
0
Goal
- The kube-apiserver must have access to the configured token issuer URL in order to verify a particular token.
- The well-known for issuer provides additional URLs that are contacted and trusted. at least the jwksURL, not sure if others are the userInfo URL and token URL are used by kube.
Why is this important?
- without this access, the kube-apiserver unable to validate the token signatures
Scenarios
- ...
Acceptance Criteria
- Dev - Has a valid enhancement if necessary
- CI - MUST be running successfully with tests automated
- QE - covered in Polarion test plan and tests implemented
- Release Technical Enablement - Must have TE slides
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Technical Enablement <link to Feature Enablement Presentation>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Enhancement merged: <link to meaningful PR or GitHub Issue>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
