staging registry for kubernetes/website

[BenTheElder]

We require a staging registry / cloud-build project for kubernetes/website to publish a build image (hugo + other deps).

Background: kubernetes/website has a containerized build environment for building the site.
In the past a simple hugo binary on the host at the correct version was sufficient, but with the docsy migration npm / postcss / autoprefixer are also required. Additionally recent changes are leading to "Too many open files" on darwin.

In order to facilitate standardizing development on the containerized environment, we should publish the website environment image pre-built. Currently contributors must manually invoke a target to build the image locally and then it is used in other targets.

see: kubernetes/website#22515, kubernetes/website#22518

[BenTheElder]

cc @dims @spiffxp

[dims]

+1 i'd support this @BenTheElder

[BenTheElder]

should I just PR this? I forgot what all we need to do to act on something like this.

[BenTheElder]

cc @jimangel

[jimangel]

I'm not sure the approval process, but I'm in support of moving this forward if other folks agree.

[spiffxp]

should I just PR this? I forgot what all we need to do to act on something like this.

Yes, follow instructions here https://github.com/kubernetes/k8s.io/tree/master/k8s.gcr.io#creating-staging-repos