Create dra-example-driver staging repo

[nojnhuh]

This PR adds a staging repo to publish images built from https://github.com/kubernetes-sigs/dra-example-driver

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nojnhuh
Once this PR has been reviewed and has the lgtm label, please assign xmudrii for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS
• groups/OWNERS

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

[nojnhuh]

FYI @bart0sh @elezar @klueska @pohly @byako

[bart0sh]

/lgtm

[pohly]

@nojnhuh: what about adding yourself?

I certainly hope that you will continue to help with maintaining this! 😉

[nojnhuh]

Yep I can definitely add myself! Should I include myself in the OWNERS file added here too?

[nojnhuh]

I added myself here but not in the OWNERS file, which I understand means something different.

[pohly]

I think it's fine to also have you there. If I remember correctly, we trigger image promotion by creating and updating files there. It seems reasonable to grant you the right to approve that when you also have permission to do that manually.

[nojnhuh]

Sounds good, done!

[pohly]

Where do all these registry names come from? How do we keep them up-to-date in the future?

[nojnhuh]

I originally pulled this list from another image here: https://github.com/kubernetes/k8s.io/blob/4baba73c2b3c999fb7b217536981096bd3d0d83a/registry.k8s.io/manifests/k8s-staging-lws/promoter-manifest.yaml

Though it seems like the pattern from the cloud-provider-kind image here is slightly more up to date, so I've updated it here to match this: https://github.com/kubernetes/k8s.io/blob/14b4586d8809e2c12fd6847c0caad07c7b3168b8/registry.k8s.io/manifests/k8s-staging-cloud-provider-kind/promoter-manifest.yaml

That doesn't change the set of repos though, which I think sig-k8s-infra manages, e.g. #6322

[pohly]

Okay, so this is maintained my someone (in this case, probably literally one person). As long as it's not me I'm okay with this 😅

[k8s-ci-robot]

@nojnhuh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-k8sio-cip	a689190	link	true	/test pull-k8sio-cip

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[pohly]

/lgtm

pull-k8sio-cip failed, but with no information. Unrelated?

[pohly]

/assign @xmudrii

For approval.