Give Amy Chen access to pushing to cluster-api staging registry

[amy]

Reference Issue: kubernetes-sigs/cluster-api-provider-aws#795
Summary: I would like to smooth out the release process for cluster-api and need access to pushing images to the staging registry.

[k8s-ci-robot]

Welcome @amy!

It looks like this is your first PR to kubernetes/k8s.io 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/k8s.io has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @amy. 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.

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.

[amy]

cc/ @dims @chuckha

[amy]

/ok-to-test

[k8s-ci-robot]

@amy: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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.

[dims]

/ok-to-test

[dims]

@amy can you please get a +1/lgtm from one of the leads?

[dims]

/assign

[chuckha]

@timothysc or @justinsb, can you give a +1 here? This work will allow more than just you to push new release container images for cluster-api :D

[dims]

@chuckha your +1 is good enough since you are already in the group.

/approve
/lgtm

[nikhita]

🎉 🎉 🎉

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [dims,nikhita]

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

[cblecker]

Ran the update for this.

[thockin]

Are these staging repos now actively being used? That would be good to know so they don't get nuked as we iterate on setup...

…

On Wed, May 29, 2019 at 10:38 PM Kubernetes Prow Robot < ***@***.***> wrote: Merged #268 <#268> into master. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#268?email_source=notifications&email_token=ABKWAVEQBEUDEHB4LSBABL3PX5R4ZA5CNFSM4HQUIY22YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORWYEUAA#event-2377140736>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABKWAVHU4HR6TDEVZIIXZLTPX5R4ZANCNFSM4HQUIY2Q> .