Sync supported service account token algorithms to test image

[liggitt]

What type of PR is this?

/kind cleanup
/kind failing-test

What this PR does / why we need it:

Updates the test image to support all the algorithms we support for signing service account tokens.

Which issue(s) this PR is related to:

#141010

Does this PR introduce a user-facing change?

NONE

/sig auth testing

[kubernetes-prow]

Please note that we're already in Code Freeze for the upcoming v1.37.0 release.

Adding the milestone to this PR is strictly prohibited without proper approval. If this PR needs to be included in the v1.37.0 release:

1. Technical review: get the PR reviewed and approved as usual (/lgtm and /approve)
2. Inclusion in release: ping @sig-release-leads on the #sig-release Slack channel and suggest to add the v1.37.0 milestone to the PR

[kubernetes-prow]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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-sigs/prow repository.

[dims]

/approve
/lgtm

@liggitt should we add the milestone? since it is breaking external folks running conformance

cc @kubernetes/release-team-leads

[kubernetes-prow]

LGTM label has been added.

Details

Git tree hash: d29a6005cb7ec2516d3e17b4b335ab410689f3fc

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, liggitt

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• pkg/serviceaccount/OWNERS [dims,liggitt]
• test/images/agnhost/OWNERS [dims,liggitt]

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

[liggitt]

I'd be supportive of that (and actually of backporting a test-only change like this)

@kubernetes/release-managers @kubernetes/cncf-conformance-wg thoughts?

[dims]

Let's do this! we are just adding additional entries and no change in logic.

/milestone v1.37

[liggitt]

thanks ... it's been a while since I've bumped agnhost ... do we have to trigger a build / release / bump ourselves?

[dims]

https://prow.k8s.io/?job=*agnhost* should have worked, but that's facing a different problem w.r.t gcb-docker-gcloud that @upodroid is chasing in kubernetes/release#4481

[liggitt]

do we need to bump an agnhost version in test/images/agnhost/VERSION before that will trigger a new build, or does it build automatically from master and we just have to promote a build to a tag?

[cbf123]

is there additional work needed to make this work on 1.36? There was a previous comment about backporting the change.