Hi @Joseph,
This should work out of the box. I haven’t tested the full cycle, you will have to determine how to update your Kubernetes commands to direct the requests to your Nexus Repository Manager rather than gcr.io. Once you do that, the following configuration should suffice:
Create a new Docker proxy repository to https://k8s.gcr.io, with the remainder of the parameters set to the defaults.
I then added that new proxy repository to a group repository that I had previously set up. I can now pull a kube* image from that group and observe that the tag and layer are cached. kube-proxy-amd64 doesn’t look like it has a “latest” tag, so I had to explicitly specify the version of the image (local-mike is a hostname that I have created for the server that my Nexus Repo is running, and 19443 is the HTTPS port that I have configured in Nexus Repo for my Group Repository):
$ docker pull local-mike:19443/kube-proxy-amd64:v1.10.11
v1.10.11: Pulling from kube-proxy-amd64
Digest: sha256:e1fe1f33988821d0dd1e7852422b525415a5b748f768e9e9089474ca71bf350c
Status: Downloaded newer image for local-mike:19443/kube-proxy-amd64:v1.10.11
