Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update example URLs after nginx is the only implementation in repo #1510

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion examples/daemonset/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ In some cases, the Ingress controller will be required to be run at all the node
The default backend is a service of handling all url paths and hosts the nginx controller doesn't understand. Deploy the default-http-backend as follow:

```console
$ kubectl apply -f ../../deployment/nginx/default-backend.yaml
$ kubectl apply -f ../../deployment/default-backend.yaml
deployment "default-http-backend" configured
service "default-http-backend" configured

Expand Down
2 changes: 1 addition & 1 deletion examples/deployment/kubeadm/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ The Nginx Ingress Controller uses nginx (surprisingly!) to loadbalance requests
ports 80 and 443 to Services in the cluster.

```console
$ kubectl apply -f https://rawgit.com/kubernetes/ingress/master/examples/deployment/nginx/kubeadm/nginx-ingress-controller.yaml
$ kubectl apply -f https://rawgit.com/kubernetes/ingress/master/examples/deployment/kubeadm/nginx-ingress-controller.yaml
deployment "default-http-backend" created
service "default-http-backend" created
deployment "nginx-ingress-controller" created
Expand Down
8 changes: 4 additions & 4 deletions examples/rbac/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,20 +89,20 @@ change as well.
`ClusterRoleBinding`, and `RoleBinding`.

```sh
kubectl create -f https://raw.githubusercontent.com/kubernetes/ingress/master/examples/rbac/nginx/nginx-ingress-controller-rbac.yml
kubectl create -f https://raw.githubusercontent.com/kubernetes/ingress/master/examples/rbac/nginx-ingress-controller-rbac.yml
```

2. Create default backend
```sh
kubectl create -f https://raw.githubusercontent.com/kubernetes/ingress/master/examples/rbac/nginx/default-backend.yml
kubectl create -f https://raw.githubusercontent.com/kubernetes/ingress/master/examples/rbac/default-backend.yml
```

3. Create the nginx-ingress-controller

For this example to work, the Service must be in the nginx-ingress namespace:

```sh
kubectl create -f https://raw.githubusercontent.com/kubernetes/ingress/master/examples/rbac/nginx/nginx-ingress-controller.yml
kubectl create -f https://raw.githubusercontent.com/kubernetes/ingress/master/examples/rbac/nginx-ingress-controller.yml
```

The serviceAccountName associated with the containers in the deployment must
Expand All @@ -112,5 +112,5 @@ should be in the nginx-ingress namespace.

4. Create ingress service
```sh
kubectl create -f https://raw.githubusercontent.com/kubernetes/ingress/master/examples/rbac/nginx/nginx-ingress-controller-service.yml
kubectl create -f https://raw.githubusercontent.com/kubernetes/ingress/master/examples/rbac/nginx-ingress-controller-service.yml
```
2 changes: 1 addition & 1 deletion examples/scaling-deployment/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ This example aims to demonstrate the Deployment of multi nginx ingress controlle
The default backend is a service of handling all url paths and hosts the nginx controller doesn't understand. Deploy the default-http-backend as follow:

```console
$ kubectl apply -f ../../deployment/nginx/default-backend.yaml
$ kubectl apply -f ../../deployment/default-backend.yaml
deployment "default-http-backend" configured
service "default-http-backend" configured

Expand Down