Uploaded image for project: 'Agent-based Installer for OpenShift'
  1. Agent-based Installer for OpenShift
  2. AGENT-1448

Installer - Create IRI registry credentials and merge into pull secret

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • 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:

      This requires/does not require a design proposal.
      This requires/does not require a feature gate.

              rwsu1@redhat.com Richard Su
              rwsu1@redhat.com Richard Su
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: