This is the repository for Kubernetes DNS.
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.
- Build and test (
make images-clean
;make build
;make containers
;make test
) - Update go dependencies if needed.
- Update the release tag. We use semantic versioning to name releases.
- 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 viagcloud 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 ingcr.io/k8s-staging-dns
. Status for build jobs can be checked at - https://k8s-testgrid.appspot.com/sig-network-dns#dns-push-images - Promote the images to
gcr.io/k8s-artifacts-prod
using the process described in this link. The image SHAs should be added toimages/k8s-staging-dns/images.yaml
. - Submit a PR for the kubernetes/kubernetes repository to switch to the new version of the containers.
- Images will be available in the repo k8s.gcr.io/dns/. The node-cache image with tag 1.15.14 can be found at k8s.gcr.io/dns/k8s-dns-node-cache:1.15.14. Older versions are at k8s.gcr.io/k8s-dns-node-cache: