Add OWNERS for k8s.gcr.io/k8s-staging-capi-openstack

[sbueringer]

Adds OWNERS files for capo related staging directories. Approvers are based on the active approvers for the code repo: https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/master/OWNERS_ALIASES#L21

[k8s-ci-robot]

Hi @sbueringer. Thanks for your PR.

I'm waiting for a kubernetes 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.

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/test-infra repository.

[sbueringer]

@dims

The following users are mentioned in OWNERS file(s) but are not members of the kubernetes org.

Once all users have been added as members of the org, you can trigger verification by writing /verify-owners in a comment.

• sbueringer

  • k8s.gcr.io/k8s-staging-capi-openstack/OWNERS

• jichenic

  • k8s.gcr.io/k8s-staging-capi-openstack/OWNERS

@dims We are both members of the kubernetes-sigs org. I saw a discussion a while ago about if a membership in one of the Kubernetes orgs (kubernetes and kubernetes-sigs) implies the same in the other org. Do you know what the current status is?

[dims]

@sbueringer can you please open an issue in https://github.com/kubernetes/org/ to ask? (also jichenic should be @jichenjc right?)

[sbueringer]

/verify-owners

[sbueringer]

@sbueringer can you please open an issue in https://github.com/kubernetes/org/ to ask? (also jichenic should be @jichenjc right?)

Yup, you're right, I adjusted the OWNER file. Now it's only me who is missing in the Kubernetes org :). I've opened an issue here: kubernetes/org#1169

[sbueringer]

/verify-owners

[sbueringer]

@dims Prow is happy now :), not sure if there's anything else to do from my side

[dims]

/ok-to-test
/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims

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:

• OWNERS [dims]

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