DevFW-CICD/ingress-nginx-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix broken links in documentation (#4746)

Browse source
This commit is contained in:
Manuel Alejandro de Brito Fontes 2019-11-08 16:22:52 -03:00 • committed by GitHub
parent 2771095b8c
commit d1eea794e9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
9 changed files with 23 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/development.md
View file

@ -20,7 +20,7 @@ cd ingress-nginx
### Initial developer environment build
>**Prequisites**: Minikube must be installed.
See [releases](https://github.com/kubernetes/minikube/releases) for installation instructions.
See [releases](https://github.com/kubernetes/minikube/releases) for installation instructions.
If you are using **MacOS** and deploying to **minikube**, the following command will build the local nginx controller container image and deploy the ingress controller onto a minikube cluster with RBAC enabled in the namespace `ingress-nginx`:
@ -55,8 +55,8 @@ Check the version of `dep` you are using and make sure it is up to date.
$ dep version
dep:
version : devel
build date :
git hash :
build date :
git hash :
go version : go1.9
go compiler : gc
platform : linux/amd64
@ -134,7 +134,7 @@ $ TAG=<tag> REGISTRY=$USER/ingress-controller make push
## Deploying
There are several ways to deploy the ingress controller onto a cluster.
Please check the [deployment guide](./deploy)
Please check the [deployment guide](../deploy/)
## Testing
@ -152,7 +152,7 @@ $ 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 [Building the e2e test image](./Building the e2e test image)
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:
@ -162,7 +162,7 @@ $ ./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.
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.
## Releasing