-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
Not Selected
-
-
-
Agent Sprint 285
User Story:
As a (user persona), I want to be able to:
- have the IRI registry access be authenticated
so that I can
- restrict access to the registry
Acceptance Criteria:
Description of criteria:
- Generate IRI registry credentials (username: openshift, 32-byte random password with bcrypt hash)
- Create Secret manifest “iri-registry-auth” in openshift-machine-config-operator namespace
- Secret contains: htpasswd field (bcrypt hash) and password field (plaintext for pull secret)
- Update agent ignition asset to merge IRI credentials into pull secret
- Credentials stored in Docker config JSON format at registry hostname api-int.<cluster-domain>:22625
- The credentials are merged into the global pull secret at runtime when assisted-service calls openshift-install to create the ignition files
(optional) Out of Scope:
Does not add credentials to the IRI registry running on the live ISO.
Engineering Details:
- (optional) https://github/com/link.to.enhancement/
- (optional) https://issues.redhat.com/link.to.spike
- Engineering detail 1
- Engineering detail 2
This requires/does not require a design proposal.
This requires/does not require a feature gate.