Add kube-state-metrics staging repo

[brancz]

This adds a kube-state-metrics staging repo so we can stop using external registries and/or have to ping people working at google to publish images.

I'm not entirely sure I've done everything correctly, but I believe I followed these steps: https://github.com/kubernetes/k8s.io/tree/master/k8s.gcr.io#staging-repos

Let me know if this is everything that is needed. 🙂

cc @cblecker @nikhita @lilic @tariq1890

[k8s-ci-robot]

Welcome @brancz!

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. 😃

[tariq1890]

If I understand correctly, we use two registry repos then? Staging and Production?

[nikhita]

If I understand correctly, we use two registry repos then? Staging and Production?

Eventually, yes.

Right now the tool used to promote images is WIP so we just use the staging repo. When it is ready, we can start having prod ones too.

[brancz]

I believe all comments are resolved. Please take a look. 🙂

[lilic]

lgtm to me :)

[nikhita]

@dims @thockin ping :)

[nikhita]

I'm realllyyyyyy sorry about the back and forth dance on this, but while working on #399, I realized that using kube-state-metrics would be fine since we'll need to count the character length with the k8s-staging- prefix, not k8s-infra-staging- prefix. 🙈

k8s-staging-kube-state-metrics is exactly 30 characters (and that's the maximum value allowed).

• k8s-staging- prefix is used in the manifest file, which is the one gcloud complains about.
• k8s-infra-staging- prefix is used for google groups, and google groups doesn't complain about the character length.

[brancz]

Got it. Will update this in a bit then!

[brancz]

Done.

[tariq1890]

Thanks @nikhita !

One of the owners just removed their request for review :(.
/assign @cblecker

[tariq1890]

@brancz I think you need to maintain lexical order here. As stated in the comment above.

[brancz]

Done

[dims]

Apologies! i was cleaning my PR queue and lost this one.

@brancz please fix the lexical order as @tariq1890 mentions and ping me on slack and i'll get this in.

/assign

[brancz]

Done! Thanks! Let me know if there is anything else 🙂 .

[dims]

/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

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