From bcc7d98d8e89c68f09ee0de11bc19f272d01e0a5 Mon Sep 17 00:00:00 2001 From: Manuel Alejandro de Brito Fontes Date: Sat, 4 Jan 2020 15:56:25 -0300 Subject: [PATCH] Use yaml files from a particular tag, not from master --- docs/deploy/index.md | 20 ++++++++++---------- docs/examples/psp/README.md | 6 +++--- 2 files changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/deploy/index.md b/docs/deploy/index.md index 99b05902aa..98c076c9e7 100644 --- a/docs/deploy/index.md +++ b/docs/deploy/index.md @@ -34,7 +34,7 @@ The following **Mandatory Command** is required for all deployments. ```console -kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/mandatory.yaml +kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/mandatory.yaml ``` !!! tip @@ -53,7 +53,7 @@ Kubernetes is available in Docker for Mac (from [version 18.06.0-ce](https://doc Create a service ```console -kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/cloud-generic.yaml +kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/provider/cloud-generic.yaml ``` #### minikube @@ -102,8 +102,8 @@ Check that no change is necessary with regards to the ELB idle timeout. In some Then execute: ```console -kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/aws/service-l4.yaml -kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/aws/patch-configmap-l4.yaml +kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/provider/aws/service-l4.yaml +kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/provider/aws/patch-configmap-l4.yaml ``` For L7: @@ -115,8 +115,8 @@ Check that no change is necessary with regards to the ELB idle timeout. In some Then execute: ```console -kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/aws/service-l7.yaml -kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/aws/patch-configmap-l7.yaml +kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/provider/aws/service-l7.yaml +kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/provider/aws/patch-configmap-l7.yaml ``` This example creates an ELB with just two listeners, one in port 80 and another in port 443 @@ -137,13 +137,13 @@ More information with regards to idle timeouts for your Load Balancer can be fou This type of load balancer is supported since v1.10.0 as an ALPHA feature. ```console -kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/aws/service-nlb.yaml +kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/provider/aws/service-nlb.yaml ``` #### GCE-GKE ```console -kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/cloud-generic.yaml +kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/provider/cloud-generic.yaml ``` **Important Note:** proxy protocol is not supported in GCE/GKE @@ -151,7 +151,7 @@ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/mast #### Azure ```console -kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/cloud-generic.yaml +kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/provider/cloud-generic.yaml ``` #### Bare-metal @@ -159,7 +159,7 @@ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/mast Using [NodePort](https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport): ```console -kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/baremetal/service-nodeport.yaml +kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/provider/baremetal/service-nodeport.yaml ``` !!! tip diff --git a/docs/examples/psp/README.md b/docs/examples/psp/README.md index 1061794903..2164f0a09e 100644 --- a/docs/examples/psp/README.md +++ b/docs/examples/psp/README.md @@ -2,7 +2,7 @@ In most clusters today, by default, all resources (e.g. Deployments and ReplicatSets) have permissions to create pods. -Kubernetes however provides a more fine-grained authorization policy called +Kubernetes however provides a more fine-grained authorization policy called [Pod Security Policy (PSP)](https://kubernetes.io/docs/concepts/policy/pod-security-policy/). PSP allows the cluster owner to define the permission of each object, for example creating a pod. @@ -15,8 +15,8 @@ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/mast ``` Now that the pod security policy is applied, we can continue as usual by applying the -[mandatory.yaml](https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/mandatory.yaml) -according to the [Installation Guide](../../deploy/index.md). +[mandatory.yaml](https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.26.2/deploy/static/mandatory.yaml) +according to the [Installation Guide](../../deploy/index.md). Note: PSP permissions must be granted before to the creation of the Deployment and the ReplicaSet. If the Deployment or ReplicaSet already exist, they will receive the PSP permissions