Question

Using a custom DNS name server with managed Kubernetes

I’m very new to Kubernetes and I’m trying to pull a container from a private container registry.

The private container registry hostname is internal and only resolvable using our internal DNS.

Failed to pull image “this.is.private/awesome:latest”: rpc error: code = Unknown desc = Error response from daemon: Get https://this.is.private/v2/: dial tcp: lookup this.is.private on 67.207.67.2:53: no such host

How can I tell Kubernetes to use our internal DNS name server when it tries to resolve this.is.private?

Remember: this is a managed instance of Kubernetes and this error is before the pods are online.

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer