ingress-nginx-helm/images/404-server
2018-10-07 23:05:23 +08:00
..
Godeps Update go dependencies 2017-08-16 09:12:47 -03:00
vendor/github.com Update go dependencies 2017-08-16 09:12:47 -03:00
.gitignore Update go dependencies 2017-08-16 09:12:47 -03:00
cloudbuild.yaml [404-server] conceal /metrics behind port 10254 2018-09-26 16:02:18 -04:00
Dockerfile Add 404-server (defaultbackend) 2017-08-14 18:57:43 -04:00
Makefile [404-server] conceal /metrics behind port 10254 2018-09-26 16:02:18 -04:00
metrics.go Add 404-server (defaultbackend) 2017-08-14 18:57:43 -04:00
OWNERS Update 404 server 2017-10-22 11:31:50 -03:00
README.md Add 404-server (defaultbackend) 2017-08-14 18:57:43 -04:00
server.go remove duplication 2018-10-07 23:05:23 +08:00

404-server (default backend)

404-server is a simple webserver that satisfies the ingress, which means it has to do two things:

  1. Serves a 404 page at /
  2. Serves 200 on a /healthz

How to release:

The 404-server Makefile supports multiple architectures, which means it may cross-compile and build an docker image easily. If you are releasing a new version, please bump the TAG value in the Makefile before building the images.

How to build and push all images:

# Build for linux/amd64 (default)
$ make push
$ make push ARCH=amd64
# ---> gcr.io/google_containers/defaultbackend-amd64:TAG

$ make push-legacy ARCH=amd64
# ---> gcr.io/google_containers/defaultbackend:TAG (image with backwards compatible naming)

$ make push ARCH=arm
# ---> gcr.io/google_containers/defaultbackend-arm:TAG

$ make push ARCH=arm64
# ---> gcr.io/google_containers/defaultbackend-arm64:TAG

$ make push ARCH=ppc64le
# ---> gcr.io/google_containers/defaultbackend-ppc64le:TAG

Of course, if you don't want to push the images, just run make container