rongfu.leng

Thank you very much, I am interested, I will first understand the current situation and see what I can contribute to it. @jerop

@milosgajdos Can we discuss this issue?

> I think it's a sensible idea, I would suggest worrying down the design first before starting writing the code. yes, I can design first, and at the same time...

The proxy configuration is adjusted as follows： ``` proxy: - name: k8s-proxy remoteurl: https://registry.k8s.io username: [username] password: [password] - name: hub-proxy remoteurl: https://hub.docker.io username: [username] password: [password] - name: /...

Regarding compatibility with past configurations, I don't have much idea. because this structure changes too much, mapping from one `registry` to one `proxy` to one `registry` mapping multiple `proxy`, this...

> proxy: > mappings: > - path: dockerhub > remoteurl: https://hub.docker.io I like this style.

> > Please, the idea of "proxy a subset of a remote registry" can be said in more detail. > > > > If we want to proxy just one...

> Also, `subPath` might be better as `namespaces`, which I've seen used as a term for organising registries. Then the structure of this configuration is defined as follows ```yaml proxy:...

> Great! > > Some more thoughts, would this be valid to be able to rename remote namespaces into the proxy? > > ``` > proxy: > mappings: > -...

I mean how to get the value of namespaces from image url.