Hands-On Microservices with Kubernetes

Safeguarding your image registry

It is highly recommended to use private image registries. If you have proprietary code, then you must not publish your containers with public access because reverse-engineering your images will grant attackers access. However, there are other reasons for this too. You get better control over (and auditing of) pulling and pushing images from the registry.

There are two options here:

• Use a private registry managed by a third party like AWS, Google, Microsoft, or Quay.
• Use your own private registry.

The first option makes sense if you deploy your system on a cloud platform that has good integration with its own image registry or if you don't manage your own registry in the sprint of cloud-native computing and ...