Need help with dns?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

656 Stars 369 Forks Apache License 2.0 602 Commits 11 Opened issues


Kubernetes DNS service

Services available


Need anything else?

Contributors list

Kubernetes DNS

Build Status Coverage Status Go Report Card

This is the repository for Kubernetes DNS.




| target | description | | ---- | ---- | |all, build | build all binaries | |test | run unit tests | |containers | build the containers | |images-clean | clear image build artifacts from workdir | |push | push containers to the registry | |help | this help message | |version | show package version | |{build,containers,push}-ARCH | do action for specific ARCH | |all-{build,containers,push} | do action for all ARCH | |only-push-BINARY | push just BINARY |

  • Setting
    will show additional build logging.
  • Setting
    will override the container version tag.

Vulnerability patching

Vulnerability patches are mainly for debian-base or debian-iptables images. They can be updated to the latest by modifying and dnsmasq Makefile. Example PR.

Once the PR has merged, a new release tag should be cut. The rest of the release process is described below.

Release process

  1. Build and test (
    make images-clean
    make build
    make containers
    make test
  2. To build just the node-cache container, use
    make containers CONTAINER_BINARIES=node-cache
  3. The same steps are executed via the presubmit script
    which is run by the test-infra prow job.
  4. Update go dependencies if needed.
  5. Update the release tag. We use semantic versioning to name releases.
  6. Wait for container images to be pushed via cloudbuild yaml. This will be done automatically by
    . A manual cloud build can be submitted via
    gcloud builds submit --config cloudbuild.yaml
    , but this requires owner permissions in k8s-staging-dns project. The automated job pushes images for all architectures and makes them available in
    . Status for build jobs can be checked at -
  7. Promote the images to
    using the process described in this link. The image SHAs should be added to
  8. Submit a PR for the kubernetes/kubernetes repository to switch to the new version of the containers.
  9. Images will be available in the repo The node-cache image with tag 1.15.14 can be found at Older versions are at

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.