Story (Required)

As a user trying to use the tekton cache step actions I want to be able to use a secrets of type kubernetes.io/dockerconfigjson.

This type of secret is very common as it can easily be created by kubectl (and other tools) from existing .docker/config.json files.

There is several task that already support it (in addition to a standard secret with a config.json key.

Background (Required)

N/A

Out of scope

N/A

Approach (Required)

See the following examples

• https://github.com/openshift-pipelines/task-containers/blob/main/scripts/buildah-bud.sh#L43

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

I can use a kubernetes.io/dockerconfigjson with the tekton cache step action

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met