Epic Goal

• The installation docs (and everywhere else) are extracting the ccoctl binary directly from the release image
  • oc adm release extract --command='ccoctl.rhel8' ${RELEASE_IMAGE}
  • ccoctl, ccoctl.rhel8, ccoctl.rhel9
• The installation docs are using the --included and --install-config parameters of when using oc to extract credentialRequests
• The installation doc steps for oc extract credentialRequests happens after all install-config modifications so --included is most accurate
• The installation docs have ccoctl using the same directory as openshift-install
  • and are no longer having the user copy the files

Why is this important?

• To improve the user experience when installing clusters with short-term token authentication.

Scenarios

Acceptance Criteria

Dependencies (internal and external)

Previous Work (Optional):

Open questions::

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>