Open antonin-a opened 9 months ago
A must have for public k8s adoption. Indeed, "private" docker registry should come with private network access.
As a MKS user, i need my nodes to be able to access the MPR via vRack only. But as a developper i need to push new images on my MPR from a restricted range (whitelist) of public IP addresses.
So i need to have a public IP + a private IP (network) on my MPR instance. And then i need to be able to whitelist CIDR IPs on both sides.
As a Managed Private Registry user I would like to be able to expose my registry on my private network (vRack) so that it is not exposed on internet and I can access it directly from my k8s nodes on a private way.
Please react to this Feature Request by adding a thumb up and do not hesitate to comment to show your interest and/or share your use cases !