by kubernetes

kubernetes /dns

Kubernetes DNS service

485 Stars 289 Forks Last release: over 1 year ago (1.15.4) Apache License 2.0 478 Commits 34 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

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.


Release process

  1. Build and test (
    make images-clean
    make build
    make containers
    make test
  2. Update go dependencies if needed.
  3. Update the release tag. We use semantic versioning to name releases.
  4. 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 - https://k8s-testgrid.appspot.com/sig-network-dns#dns-push-images
  5. Promote the images to
    using the process described in this link. The image SHAs should be added to
  6. Submit a PR for the kubernetes/kubernetes repository to switch to the new version of the containers.

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.