同步操作将从 Djk/ingress-nginx 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
This document explains how to get started with developing for NGINX Ingress controller. It includes how to build, test, and release ingress controllers.
The code must be checked out as a subdirectory of k8s.io, and not github.com.
mkdir -p $GOPATH/src/k8s.io
cd $GOPATH/src/k8s.io
# Replace "$YOUR_GITHUB_USERNAME" below with your github username
git clone https://github.com/$YOUR_GITHUB_USERNAME/ingress-nginx.git
cd ingress-nginx
Ensure docker experimental features option is enabled for buildx
$ make dev-env
The nginx controller container image can be rebuilt using:
$ ARCH=amd64 TAG=dev REGISTRY=$USER/ingress-controller make build container
The image will only be used by pods created after the rebuild. To delete old pods which will cause new ones to spin up:
$ kubectl get pods -n ingress-nginx
$ kubectl delete pod -n ingress-nginx nginx-ingress-controller-<unique-pod-id>
The build uses dependencies in the vendor
directory, which
must be installed before building a binary/image. Occasionally, you
might need to update the dependencies.
This guide requires you to install go 1.13 or newer.
This will automatically save the dependencies to the vendor/
directory.
$ go get
$ make dep-ensure
All ingress controllers are built through a Makefile. Depending on your requirements you can build a raw server binary, a local container image, or push an image to a remote repository.
In order to use your local Docker, you may need to set the following environment variables:
# "gcloud docker" (default) or "docker"
$ export DOCKER=<docker>
# "quay.io/kubernetes-ingress-controller" (default), "index.docker.io", or your own registry
$ export REGISTRY=<your-docker-registry>
To find the registry simply run: docker system info | grep Registry
The e2e test image can also be built through the Makefile.
$ make e2e-test-image
You can then make this image available on your minikube host by exporting the image and loading it with the minikube docker context:
$ docker save nginx-ingress-controller:e2e | (eval $(minikube docker-env) && docker load)
Build a raw server binary
$ make build
TODO: add more specific instructions needed for raw server binary.
Build a local container image
$ TAG=<tag> REGISTRY=$USER/ingress-controller make container
Push the container image to a remote repository
$ TAG=<tag> REGISTRY=$USER/ingress-controller make push
There are several ways to deploy the ingress controller onto a cluster. Please check the deployment guide
To run unit-tests, just run
$ cd $GOPATH/src/k8s.io/ingress-nginx
$ make test
If you have access to a Kubernetes cluster, you can also run e2e tests using ginkgo.
$ cd $GOPATH/src/k8s.io/ingress-nginx
$ make e2e-test
NOTE: if your e2e pod keeps hanging in an ImagePullBackoff, make sure you've made your e2e nginx-ingress-controller image available to minikube as explained in the Building the e2e test image section
To run unit-tests for lua code locally, run:
$ cd $GOPATH/src/k8s.io/ingress-nginx
$ ./rootfs/etc/nginx/lua/test/up.sh
$ make lua-test
Lua tests are located in $GOPATH/src/k8s.io/ingress-nginx/rootfs/etc/nginx/lua/test
. When creating a new test file it must follow the naming convention <mytest>_test.lua
or it will be ignored.
All Makefiles will produce a release binary, as shown above. To publish this
to a wider Kubernetes user base, push the image to a container registry, like
gcr.io. All release images are hosted under gcr.io/google_containers
and
tagged according to a semver scheme.
An example release might look like:
$ make release
Please follow these guidelines to cut a release:
controller-release-version
. Typically, pre-releases are cut from HEAD.
All major feature work is done in HEAD. Specific bug fixes are
cherry-picked into a release branch.此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。