You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 

2.4 KiB

Kubernetes DNS

Build Status Coverage Status Go Report Card

This is the repository for Kubernetes DNS.

Images

Building

make targets:

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 VERBOSE=1 will show additional build logging.
  • Setting VERSION will override the container version tag.

Analytics

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 k8s.io/test-infra/.../k8s-staging-dns.yaml. 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 gcr.io/k8s-staging-dns.
  5. Promote the images to gcr.io/k8s-artifacts-prod using the process described in this link. The image SHAs should be added to images/k8s-staging-dns/images.yaml.
  6. Submit a PR for the kubernetes/kubernetes repository to switch to the new version of the containers.