Bundle resolver can use ServiceAccount for auth

[wilstdu]

Changes

• Bundles resolver can read image pull secrets from ServiceAccount via attached secret and directly from specified Secret.

With #7159 change ECR private registry users no longer had an easy option to authenticate with ECR, because ECR uses short-lived credentials (up to 12 hours), therefore adding it to a secret doesn't make sense because it would mean implementing an additional mechanism to secret rotation in each namespace.

Fixes: #7854
Extends: #7159

Tested both variants - GCR (Secret) and ECR (ServiceAccount) private registries.

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• pre-commit Passed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Fix bundle resolver so it could pull OCI image (bundle) manifest from AWS ECR private registry

[linux-foundation-easycla]

• ✅login: wilstdu / (1f42df5)

The committers listed above are authorized under a signed CLA.

[wilstdu]

/kind bug

[tekton-robot]

Hi @wilstdu. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/resolution/resolver/bundle/params.go	92.0%	87.9%	-4.1

[vdemeester]

/ok-to-test
/cc @chitrangpatel @Yongxuanzhang @JeromeJu

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/resolution/resolver/bundle/params.go	92.0%	87.9%	-4.1

[vdemeester]

😻

[seternate]

How is the status with this PR? Would be awesome to get that in, since I would need that as well! :)

[vdemeester]

ping @tektoncd/core-maintainers

[chitrangpatel]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chitrangpatel, vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [chitrangpatel,vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment