From 635c4e33182b44ee25d88f4b2ff096e6180c27c0 Mon Sep 17 00:00:00 2001 From: k8s-ci-robot Date: Sun, 24 Oct 2021 21:39:19 +0000 Subject: [PATCH] Deploy GitHub Pages --- deploy/index.html | 2 +- sitemap.xml.gz | Bin 711 -> 711 bytes 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy/index.html b/deploy/index.html index 41f3e0c9e..1a9d9ef41 100644 --- a/deploy/index.html +++ b/deploy/index.html @@ -17,7 +17,7 @@

Scaleway

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.0.4/deploy/static/provider/scw/deploy.yaml
 

Exoscale

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/exoscale/deploy.yaml
 

The full list of annotations supported by Exoscale is available in the Exoscale Cloud Controller Manager documentation.

Oracle Cloud Infrastructure

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.0.4/deploy/static/provider/cloud/deploy.yaml
-

A complete list of available annotations for Oracle Cloud Infrastructure can be found in the OCI Cloud Controller Manager documentation.

Bare-metal

Using NodePort:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.0.4/deploy/static/provider/baremetal/deploy.yaml
+

A complete list of available annotations for Oracle Cloud Infrastructure can be found in the OCI Cloud Controller Manager documentation.

Bare-metal

Using NodePort:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.0.4/deploy/static/provider/baremetal/deploy.yaml
 

Tip

Applicable on kubernetes clusters deployed on bare-metal with generic Linux distro(Such as CentOs, Ubuntu ...).

Info

For extended notes regarding deployments on bare-metal, see Bare-metal considerations.

Verify installation

To check if the ingress controller pods have started, run the following command:

kubectl get pods -n ingress-nginx \
   -l app.kubernetes.io/name=ingress-nginx --watch
 

Once the ingress controller pods are running, you can cancel the command typing Ctrl+C.

Now, you are ready to create your first ingress.

Detect installed version

To detect which version of the ingress controller is running, exec into the pod and run nginx-ingress-controller --version.

POD_NAMESPACE=ingress-nginx
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index 38744508dac5b3faad69fd5dff707dac01300e93..b638330d1aa287d203f26aa7cab369ef2a53f033 100644
GIT binary patch
delta 14
VcmX@kdYqM2zMF%ic_Zr~CIBI=1XTb4

delta 14
VcmX@kdYqM2zMF%CZzJm=CIBB~1K