Epic Goal

• Make OCP Pull Secret and SSH Keys their own Credential type

Why is this important?

• Today, the OCP pull secret and the SSH keys are embedded within the Infrastructure provider credential.  Users with multiple infrastructure provider credentials will want to re-use pull secrets and ssh keys between them.

Scenarios

1. On the Create credential page, I can create a new Credential type for OCP Pull Secret and SSH key
2. On the Create cluster page, I can select the OCP Pull Secret and SSH key to use

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. How do we handle the existing pattern of embedded pull secret and ssh key credentials in the infra provider credential?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• 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>