Using a Private Image Registry with GKE

A simple solution to an annoying GCE Docker Issue

Issue

Kubernetes schedules a pod at node level (GCE) and kubelet on node uses Docker to download an image and run it.

Docker uses system DNS to resolve the address of a registry, because it works right on the GCE node, not in the Kubernetes. This is why…

--

--

--

CEO Objex (https://objex.tech), Rabbito.io (https://rabbito.io) and HBHM (https://hbhm.org)

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Two Weapons to Instantly Buff Your R Coding Power-Part 1

Virtual Internship At Let’s Grow More Community

Blood Splatters in Unity

Rubic Weekly Report 8/20/21

Conditionals, Booleans, Loops and Iterations in Python

No Code Evolution

12 web development trends for 2021 and beyond that you should be aware of

Most Common 3D File Formats

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Mazhar Choudhry

Mazhar Choudhry

CEO Objex (https://objex.tech), Rabbito.io (https://rabbito.io) and HBHM (https://hbhm.org)

More from Medium

Migrating to GCVE with VMware HCX — Part 1

Prometheus Metrics Scraping for Google Cloud Monitoring

Enabling Multi Dimensional pod auto scaling in Autopilot GKE is really great

Create GCP credentials: OAuth client ID, API Keys & Service Account