Deploy GitHub Pages
This commit is contained in:
k8s-ci-robot
parent
1d8b339d57
commit
4d675f3b03
5 changed files with 75 additions and 75 deletions
|
|
@ -24,7 +24,7 @@ free to use those subdirectories and get the manifest(s) related to their K8S ve
|
|||
<span class=w> </span><span class=nt>service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name</span><span class=p>:</span><span class=w> </span><span class=s>"somebucket"</span>
|
||||
<span class=w> </span><span class=nt>service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix</span><span class=p>:</span><span class=w> </span><span class=s>"ingress-nginx"</span>
|
||||
<span class=w> </span><span class=nt>service.beta.kubernetes.io/aws-load-balancer-access-log-emit-interval</span><span class=p>:</span><span class=w> </span><span class=s>"5"</span>
|
||||
</code></pre></div></p> </div> <p><strong>If you don't have Helm</strong> or if you prefer to use a YAML manifest, you can run the following command instead:</p> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0-beta.0/deploy/static/provider/cloud/deploy.yaml</span>
|
||||
</code></pre></div></p> </div> <p><strong>If you don't have Helm</strong> or if you prefer to use a YAML manifest, you can run the following command instead:</p> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0/deploy/static/provider/cloud/deploy.yaml</span>
|
||||
</code></pre></div> <div class="admonition info"> <p class=admonition-title>Info</p> <p>The YAML manifest in the command above was generated with <code>helm template</code>, so you will end up with almost the same resources as if you had used Helm to install the controller.</p> </div> <div class="admonition attention"> <p class=admonition-title>Attention</p> <p>If you are running an old version of Kubernetes (1.18 or earlier), please read <a href=#running-on-Kubernetes-versions-older-than-1.19>this paragraph</a> for specific instructions. Because of api deprecations, the default manifest may not work on your cluster. Specific manifests for supported Kubernetes versions are available within a sub-folder of each provider.</p> </div> <h3 id=firewall-configuration>Firewall configuration<a class=headerlink href=#firewall-configuration title="Permanent link"> ¶</a></h3> <p>To check which ports are used by your installation of ingress-nginx, look at the output of <code>kubectl -n ingress-nginx get pod -o yaml</code>. In general, you need:</p> <ul> <li>Port 8443 open between all hosts on which the kubernetes nodes are running. This is used for the ingress-nginx <a href=https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/ >admission controller</a>.</li> <li>Port 80 (for HTTP) and/or 443 (for HTTPS) open to the public on the kubernetes nodes to which the DNS of your apps are pointing.</li> </ul> <h3 id=pre-flight-check>Pre-flight check<a class=headerlink href=#pre-flight-check title="Permanent link"> ¶</a></h3> <p>A few pods should start in the <code>ingress-nginx</code> namespace:</p> <div class=highlight><pre><span></span><code><span class=go>kubectl get pods --namespace=ingress-nginx</span>
|
||||
</code></pre></div> <p>After a while, they should all be running. The following command will wait for the ingress controller pod to be up, running, and ready:</p> <div class=highlight><pre><span></span><code><span class=go>kubectl wait --namespace ingress-nginx \</span>
|
||||
<span class=go> --for=condition=ready pod \</span>
|
||||
|
|
@ -43,24 +43,24 @@ free to use those subdirectories and get the manifest(s) related to their K8S ve
|
|||
<span class=go> --rule www.demo.io/=demo:80</span>
|
||||
</code></pre></div> <p>You should then be able to see the "It works!" page when you connect to <a href=http://www.demo.io/ >http://www.demo.io/</a>. Congratulations, you are serving a public website hosted on a Kubernetes cluster! 🎉</p> <h2 id=environment-specific-instructions>Environment-specific instructions<a class=headerlink href=#environment-specific-instructions title="Permanent link"> ¶</a></h2> <h3 id=local-development-clusters>Local development clusters<a class=headerlink href=#local-development-clusters title="Permanent link"> ¶</a></h3> <h4 id=minikube>minikube<a class=headerlink href=#minikube title="Permanent link"> ¶</a></h4> <p>The ingress controller can be installed through minikube's addons system:</p> <div class=highlight><pre><span></span><code><span class=go>minikube addons enable ingress</span>
|
||||
</code></pre></div> <h4 id=microk8s>MicroK8s<a class=headerlink href=#microk8s title="Permanent link"> ¶</a></h4> <p>The ingress controller can be installed through MicroK8s's addons system:</p> <div class=highlight><pre><span></span><code><span class=go>microk8s enable ingress</span>
|
||||
</code></pre></div> <p>Please check the MicroK8s <a href=https://microk8s.io/docs/addon-ingress>documentation page</a> for details.</p> <h4 id=docker-desktop>Docker Desktop<a class=headerlink href=#docker-desktop title="Permanent link"> ¶</a></h4> <p>Kubernetes is available in Docker Desktop:</p> <ul> <li>Mac, from <a href=https://docs.docker.com/docker-for-mac/release-notes/#stable-releases-of-2018>version 18.06.0-ce</a></li> <li>Windows, from <a href=https://docs.docker.com/docker-for-windows/release-notes/#docker-community-edition-18060-ce-win70-2018-07-25>version 18.06.0-ce</a></li> </ul> <p>First, make sure that Kubernetes is enabled in the Docker settings. The command <code>kubectl get nodes</code> should show a single node called <code>docker-desktop</code>.</p> <p>The ingress controller can be installed on Docker Desktop using the default <a href=#quick-start>quick start</a> instructions.</p> <p>On most systems, if you don't have any other service of type <code>LoadBalancer</code> bound to port 80, the ingress controller will be assigned the <code>EXTERNAL-IP</code> of <code>localhost</code>, which means that it will be reachable on localhost:80. If that doesn't work, you might have to fall back to the <code>kubectl port-forward</code> method described in the <a href=#local-testing>local testing section</a>.</p> <h4 id=rancher-desktop>Rancher Desktop<a class=headerlink href=#rancher-desktop title="Permanent link"> ¶</a></h4> <p>Rancher Desktop provides Kubernetes and Container Management on the desktop. Kubernetes is enabled by default in Rancher Desktop.</p> <p>Rancher Desktop uses K3s under the hood, which in turn uses Traefik as the default ingress controller for the Kubernetes cluster. To use Ingress-Nginx Controller in place of the default Traefik, disable Traefik from Preference > Kubernetes menu.</p> <p>Once traefik is disabled, the Ingress-Nginx Controller can be installed on Rancher Desktop using the default <a href=#quick-start>quick start</a> instructions. Follow the instructions described in the <a href=#local-testing>local testing section</a> to try a sample.</p> <h3 id=cloud-deployments>Cloud deployments<a class=headerlink href=#cloud-deployments title="Permanent link"> ¶</a></h3> <p>If the load balancers of your cloud provider do active healthchecks on their backends (most do), you can change the <code>externalTrafficPolicy</code> of the ingress controller Service to <code>Local</code> (instead of the default <code>Cluster</code>) to save an extra hop in some cases. If you're installing with Helm, this can be done by adding <code>--set controller.service.externalTrafficPolicy=Local</code> to the <code>helm install</code> or <code>helm upgrade</code> command.</p> <p>Furthermore, if the load balancers of your cloud provider support the PROXY protocol, you can enable it, and it will let the ingress controller see the real IP address of the clients. Otherwise, it will generally see the IP address of the upstream load balancer. This must be done both in the ingress controller (with e.g. <code>--set controller.config.use-proxy-protocol=true</code>) and in the cloud provider's load balancer configuration to function correctly.</p> <p>In the following sections, we provide YAML manifests that enable these options when possible, using the specific options of various cloud providers.</p> <h4 id=aws>AWS<a class=headerlink href=#aws title="Permanent link"> ¶</a></h4> <p>In AWS, we use a Network load balancer (NLB) to expose the Ingress-Nginx Controller behind a Service of <code>Type=LoadBalancer</code>.</p> <div class="admonition info"> <p class=admonition-title>Info</p> <p>The provided templates illustrate the setup for legacy in-tree service load balancer for AWS NLB. AWS provides the documentation on how to use <a href=https://docs.aws.amazon.com/eks/latest/userguide/network-load-balancing.html>Network load balancing on Amazon EKS</a> with <a href=https://github.com/kubernetes-sigs/aws-load-balancer-controller>AWS Load Balancer Controller</a>.</p> </div> <h5 id=network-load-balancer-nlb>Network Load Balancer (NLB)<a class=headerlink href=#network-load-balancer-nlb title="Permanent link"> ¶</a></h5> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0-beta.0/deploy/static/provider/aws/deploy.yaml</span>
|
||||
</code></pre></div> <h5 id=tls-termination-in-aws-load-balancer-nlb>TLS termination in AWS Load Balancer (NLB)<a class=headerlink href=#tls-termination-in-aws-load-balancer-nlb title="Permanent link"> ¶</a></h5> <p>By default, TLS is terminated in the ingress controller. But it is also possible to terminate TLS in the Load Balancer. This section explains how to do that on AWS using an NLB.</p> <ol> <li>Download the <a href=https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0-beta.0/deploy/static/provider/aws/nlb-with-tls-termination/deploy.yaml>deploy.yaml</a> template</li> </ol> <div class=highlight><pre><span></span><code><span class=go>wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0-beta.0/deploy/static/provider/aws/nlb-with-tls-termination/deploy.yaml</span>
|
||||
</code></pre></div> <p>Please check the MicroK8s <a href=https://microk8s.io/docs/addon-ingress>documentation page</a> for details.</p> <h4 id=docker-desktop>Docker Desktop<a class=headerlink href=#docker-desktop title="Permanent link"> ¶</a></h4> <p>Kubernetes is available in Docker Desktop:</p> <ul> <li>Mac, from <a href=https://docs.docker.com/docker-for-mac/release-notes/#stable-releases-of-2018>version 18.06.0-ce</a></li> <li>Windows, from <a href=https://docs.docker.com/docker-for-windows/release-notes/#docker-community-edition-18060-ce-win70-2018-07-25>version 18.06.0-ce</a></li> </ul> <p>First, make sure that Kubernetes is enabled in the Docker settings. The command <code>kubectl get nodes</code> should show a single node called <code>docker-desktop</code>.</p> <p>The ingress controller can be installed on Docker Desktop using the default <a href=#quick-start>quick start</a> instructions.</p> <p>On most systems, if you don't have any other service of type <code>LoadBalancer</code> bound to port 80, the ingress controller will be assigned the <code>EXTERNAL-IP</code> of <code>localhost</code>, which means that it will be reachable on localhost:80. If that doesn't work, you might have to fall back to the <code>kubectl port-forward</code> method described in the <a href=#local-testing>local testing section</a>.</p> <h4 id=rancher-desktop>Rancher Desktop<a class=headerlink href=#rancher-desktop title="Permanent link"> ¶</a></h4> <p>Rancher Desktop provides Kubernetes and Container Management on the desktop. Kubernetes is enabled by default in Rancher Desktop.</p> <p>Rancher Desktop uses K3s under the hood, which in turn uses Traefik as the default ingress controller for the Kubernetes cluster. To use Ingress-Nginx Controller in place of the default Traefik, disable Traefik from Preference > Kubernetes menu.</p> <p>Once traefik is disabled, the Ingress-Nginx Controller can be installed on Rancher Desktop using the default <a href=#quick-start>quick start</a> instructions. Follow the instructions described in the <a href=#local-testing>local testing section</a> to try a sample.</p> <h3 id=cloud-deployments>Cloud deployments<a class=headerlink href=#cloud-deployments title="Permanent link"> ¶</a></h3> <p>If the load balancers of your cloud provider do active healthchecks on their backends (most do), you can change the <code>externalTrafficPolicy</code> of the ingress controller Service to <code>Local</code> (instead of the default <code>Cluster</code>) to save an extra hop in some cases. If you're installing with Helm, this can be done by adding <code>--set controller.service.externalTrafficPolicy=Local</code> to the <code>helm install</code> or <code>helm upgrade</code> command.</p> <p>Furthermore, if the load balancers of your cloud provider support the PROXY protocol, you can enable it, and it will let the ingress controller see the real IP address of the clients. Otherwise, it will generally see the IP address of the upstream load balancer. This must be done both in the ingress controller (with e.g. <code>--set controller.config.use-proxy-protocol=true</code>) and in the cloud provider's load balancer configuration to function correctly.</p> <p>In the following sections, we provide YAML manifests that enable these options when possible, using the specific options of various cloud providers.</p> <h4 id=aws>AWS<a class=headerlink href=#aws title="Permanent link"> ¶</a></h4> <p>In AWS, we use a Network load balancer (NLB) to expose the Ingress-Nginx Controller behind a Service of <code>Type=LoadBalancer</code>.</p> <div class="admonition info"> <p class=admonition-title>Info</p> <p>The provided templates illustrate the setup for legacy in-tree service load balancer for AWS NLB. AWS provides the documentation on how to use <a href=https://docs.aws.amazon.com/eks/latest/userguide/network-load-balancing.html>Network load balancing on Amazon EKS</a> with <a href=https://github.com/kubernetes-sigs/aws-load-balancer-controller>AWS Load Balancer Controller</a>.</p> </div> <h5 id=network-load-balancer-nlb>Network Load Balancer (NLB)<a class=headerlink href=#network-load-balancer-nlb title="Permanent link"> ¶</a></h5> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0/deploy/static/provider/aws/deploy.yaml</span>
|
||||
</code></pre></div> <h5 id=tls-termination-in-aws-load-balancer-nlb>TLS termination in AWS Load Balancer (NLB)<a class=headerlink href=#tls-termination-in-aws-load-balancer-nlb title="Permanent link"> ¶</a></h5> <p>By default, TLS is terminated in the ingress controller. But it is also possible to terminate TLS in the Load Balancer. This section explains how to do that on AWS using an NLB.</p> <ol> <li>Download the <a href=https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0/deploy/static/provider/aws/nlb-with-tls-termination/deploy.yaml>deploy.yaml</a> template</li> </ol> <div class=highlight><pre><span></span><code><span class=go>wget https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0/deploy/static/provider/aws/nlb-with-tls-termination/deploy.yaml</span>
|
||||
</code></pre></div> <ol> <li>Edit the file and change the VPC CIDR in use for the Kubernetes cluster:</li> </ol> <div class=highlight><pre><span></span><code>proxy-real-ip-cidr: XXX.XXX.XXX/XX
|
||||
</code></pre></div> <ol> <li>Change the AWS Certificate Manager (ACM) ID as well:</li> </ol> <div class=highlight><pre><span></span><code>arn:aws:acm:us-west-2:XXXXXXXX:certificate/XXXXXX-XXXXXXX-XXXXXXX-XXXXXXXX
|
||||
</code></pre></div> <ol> <li>Deploy the manifest:</li> </ol> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f deploy.yaml</span>
|
||||
</code></pre></div> <h5 id=nlb-idle-timeouts>NLB Idle Timeouts<a class=headerlink href=#nlb-idle-timeouts title="Permanent link"> ¶</a></h5> <p>Idle timeout value for TCP flows is 350 seconds and <a href=https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#connection-idle-timeout>cannot be modified</a>.</p> <p>For this reason, you need to ensure the <a href=https://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_timeout>keepalive_timeout</a> value is configured less than 350 seconds to work as expected.</p> <p>By default, NGINX <code>keepalive_timeout</code> is set to <code>75s</code>.</p> <p>More information with regard to timeouts can be found in the <a href=https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#connection-idle-timeout>official AWS documentation</a></p> <h4 id=gce-gke>GCE-GKE<a class=headerlink href=#gce-gke title="Permanent link"> ¶</a></h4> <p>First, your user needs to have <code>cluster-admin</code> permissions on the cluster. This can be done with the following command:</p> <div class=highlight><pre><span></span><code><span class=go>kubectl create clusterrolebinding cluster-admin-binding \</span>
|
||||
<span class=go> --clusterrole cluster-admin \</span>
|
||||
<span class=go> --user $(gcloud config get-value account)</span>
|
||||
</code></pre></div> <p>Then, the ingress controller can be installed like this:</p> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0-beta.0/deploy/static/provider/cloud/deploy.yaml</span>
|
||||
</code></pre></div> <div class="admonition warning"> <p class=admonition-title>Warning</p> <p>For private clusters, you will need to either add a firewall rule that allows master nodes access to port <code>8443/tcp</code> on worker nodes, or change the existing rule that allows access to port <code>80/tcp</code>, <code>443/tcp</code> and <code>10254/tcp</code> to also allow access to port <code>8443/tcp</code>. More information can be found in the <a href=https://cloud.google.com/load-balancing/docs/tcp/setting-up-tcp#config-hc-firewall>Official GCP Documentation</a>.</p> <p>See the <a href=https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#add_firewall_rules>GKE documentation</a> on adding rules and the <a href=https://github.com/kubernetes/kubernetes/issues/79739>Kubernetes issue</a> for more detail.</p> </div> <p>Proxy-protocol is supported in GCE check the <a href=https://cloud.google.com/load-balancing/docs/tcp/setting-up-tcp#proxy-protocol>Official Documentations on how to enable.</a></p> <h4 id=azure>Azure<a class=headerlink href=#azure title="Permanent link"> ¶</a></h4> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0-beta.0/deploy/static/provider/cloud/deploy.yaml</span>
|
||||
</code></pre></div> <p>More information with regard to Azure annotations for ingress controller can be found in the <a href=https://docs.microsoft.com/en-us/azure/aks/ingress-internal-ip#create-an-ingress-controller>official AKS documentation</a>.</p> <h4 id=digital-ocean>Digital Ocean<a class=headerlink href=#digital-ocean title="Permanent link"> ¶</a></h4> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0-beta.0/deploy/static/provider/do/deploy.yaml</span>
|
||||
</code></pre></div> <ul> <li>By default the service object of the ingress-nginx-controller for Digital-Ocean, only configures one annotation. Its this one <code>service.beta.kubernetes.io/do-loadbalancer-enable-proxy-protocol: "true"</code>. While this makes the service functional, it was reported that the Digital-Ocean LoadBalancer graphs shows <code>no data</code>, unless a few other annotations are also configured. Some of these other annotations require values that can not be generic and hence not forced in a out-of-the-box installation. These annotations and a discussion on them is well documented in <a href=https://github.com/kubernetes/ingress-nginx/issues/8965>this issue</a>. Please refer to the issue to add annotations, with values specific to user, to get graphs of the DO-LB populated with data.</li> </ul> <h4 id=scaleway>Scaleway<a class=headerlink href=#scaleway title="Permanent link"> ¶</a></h4> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0-beta.0/deploy/static/provider/scw/deploy.yaml</span>
|
||||
</code></pre></div> <p>Then, the ingress controller can be installed like this:</p> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0/deploy/static/provider/cloud/deploy.yaml</span>
|
||||
</code></pre></div> <div class="admonition warning"> <p class=admonition-title>Warning</p> <p>For private clusters, you will need to either add a firewall rule that allows master nodes access to port <code>8443/tcp</code> on worker nodes, or change the existing rule that allows access to port <code>80/tcp</code>, <code>443/tcp</code> and <code>10254/tcp</code> to also allow access to port <code>8443/tcp</code>. More information can be found in the <a href=https://cloud.google.com/load-balancing/docs/tcp/setting-up-tcp#config-hc-firewall>Official GCP Documentation</a>.</p> <p>See the <a href=https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#add_firewall_rules>GKE documentation</a> on adding rules and the <a href=https://github.com/kubernetes/kubernetes/issues/79739>Kubernetes issue</a> for more detail.</p> </div> <p>Proxy-protocol is supported in GCE check the <a href=https://cloud.google.com/load-balancing/docs/tcp/setting-up-tcp#proxy-protocol>Official Documentations on how to enable.</a></p> <h4 id=azure>Azure<a class=headerlink href=#azure title="Permanent link"> ¶</a></h4> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0/deploy/static/provider/cloud/deploy.yaml</span>
|
||||
</code></pre></div> <p>More information with regard to Azure annotations for ingress controller can be found in the <a href=https://docs.microsoft.com/en-us/azure/aks/ingress-internal-ip#create-an-ingress-controller>official AKS documentation</a>.</p> <h4 id=digital-ocean>Digital Ocean<a class=headerlink href=#digital-ocean title="Permanent link"> ¶</a></h4> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0/deploy/static/provider/do/deploy.yaml</span>
|
||||
</code></pre></div> <ul> <li>By default the service object of the ingress-nginx-controller for Digital-Ocean, only configures one annotation. Its this one <code>service.beta.kubernetes.io/do-loadbalancer-enable-proxy-protocol: "true"</code>. While this makes the service functional, it was reported that the Digital-Ocean LoadBalancer graphs shows <code>no data</code>, unless a few other annotations are also configured. Some of these other annotations require values that can not be generic and hence not forced in a out-of-the-box installation. These annotations and a discussion on them is well documented in <a href=https://github.com/kubernetes/ingress-nginx/issues/8965>this issue</a>. Please refer to the issue to add annotations, with values specific to user, to get graphs of the DO-LB populated with data.</li> </ul> <h4 id=scaleway>Scaleway<a class=headerlink href=#scaleway title="Permanent link"> ¶</a></h4> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0/deploy/static/provider/scw/deploy.yaml</span>
|
||||
</code></pre></div> <p>Refer to the <a href=https://www.scaleway.com/en/docs/tutorials/proxy-protocol-v2-load-balancer/#configuring-proxy-protocol-for-ingress-nginx>dedicated tutorial</a> in the Scaleway documentation for configuring the proxy protocol for ingress-nginx with the Scaleway load balancer.</p> <h4 id=exoscale>Exoscale<a class=headerlink href=#exoscale title="Permanent link"> ¶</a></h4> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/exoscale/deploy.yaml</span>
|
||||
</code></pre></div> <p>The full list of annotations supported by Exoscale is available in the Exoscale Cloud Controller Manager <a href=https://github.com/exoscale/exoscale-cloud-controller-manager/blob/master/docs/service-loadbalancer.md>documentation</a>.</p> <h4 id=oracle-cloud-infrastructure>Oracle Cloud Infrastructure<a class=headerlink href=#oracle-cloud-infrastructure title="Permanent link"> ¶</a></h4> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0-beta.0/deploy/static/provider/cloud/deploy.yaml</span>
|
||||
</code></pre></div> <p>The full list of annotations supported by Exoscale is available in the Exoscale Cloud Controller Manager <a href=https://github.com/exoscale/exoscale-cloud-controller-manager/blob/master/docs/service-loadbalancer.md>documentation</a>.</p> <h4 id=oracle-cloud-infrastructure>Oracle Cloud Infrastructure<a class=headerlink href=#oracle-cloud-infrastructure title="Permanent link"> ¶</a></h4> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0/deploy/static/provider/cloud/deploy.yaml</span>
|
||||
</code></pre></div> <p>A <a href=https://github.com/oracle/oci-cloud-controller-manager/blob/master/docs/load-balancer-annotations.md>complete list of available annotations for Oracle Cloud Infrastructure</a> can be found in the <a href=https://github.com/oracle/oci-cloud-controller-manager>OCI Cloud Controller Manager</a> documentation.</p> <h4 id=ovhcloud>OVHcloud<a class=headerlink href=#ovhcloud title="Permanent link"> ¶</a></h4> <div class=highlight><pre><span></span><code><span class=go>helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx</span>
|
||||
<span class=go>helm repo update</span>
|
||||
<span class=go>helm -n ingress-nginx install ingress-nginx ingress-nginx/ingress-nginx --create-namespace</span>
|
||||
</code></pre></div> <p>You can find the <a href=https://docs.ovh.com/gb/en/kubernetes/installing-nginx-ingress/ >complete tutorial</a>.</p> <h3 id=bare-metal-clusters>Bare metal clusters<a class=headerlink href=#bare-metal-clusters title="Permanent link"> ¶</a></h3> <p>This section is applicable to Kubernetes clusters deployed on bare metal servers, as well as "raw" VMs where Kubernetes was installed manually, using generic Linux distros (like CentOS, Ubuntu...)</p> <p>For quick testing, you can use a <a href=https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport>NodePort</a>. This should work on almost every cluster, but it will typically use a port in the range 30000-32767.</p> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0-beta.0/deploy/static/provider/baremetal/deploy.yaml</span>
|
||||
</code></pre></div> <p>You can find the <a href=https://docs.ovh.com/gb/en/kubernetes/installing-nginx-ingress/ >complete tutorial</a>.</p> <h3 id=bare-metal-clusters>Bare metal clusters<a class=headerlink href=#bare-metal-clusters title="Permanent link"> ¶</a></h3> <p>This section is applicable to Kubernetes clusters deployed on bare metal servers, as well as "raw" VMs where Kubernetes was installed manually, using generic Linux distros (like CentOS, Ubuntu...)</p> <p>For quick testing, you can use a <a href=https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport>NodePort</a>. This should work on almost every cluster, but it will typically use a port in the range 30000-32767.</p> <div class=highlight><pre><span></span><code><span class=go>kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.12.0/deploy/static/provider/baremetal/deploy.yaml</span>
|
||||
</code></pre></div> <p>For more information about bare metal deployments (and how to use port 80 instead of a random port in the 30000-32767 range), see <a href=baremetal/ >bare-metal considerations</a>.</p> <h2 id=miscellaneous>Miscellaneous<a class=headerlink href=#miscellaneous title="Permanent link"> ¶</a></h2> <h3 id=checking-ingress-controller-version>Checking ingress controller version<a class=headerlink href=#checking-ingress-controller-version title="Permanent link"> ¶</a></h3> <p>Run <code>/nginx-ingress-controller --version</code> within the pod, for instance with <code>kubectl exec</code>:</p> <div class=highlight><pre><span></span><code><span class=go>POD_NAMESPACE=ingress-nginx</span>
|
||||
<span class=go>POD_NAME=$(kubectl get pods -n $POD_NAMESPACE -l app.kubernetes.io/name=ingress-nginx --field-selector=status.phase=Running -o name)</span>
|
||||
<span class=go>kubectl exec $POD_NAME -n $POD_NAMESPACE -- /nginx-ingress-controller --version</span>
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
126
sitemap.xml
126
sitemap.xml
|
|
@ -2,317 +2,317 @@
|
|||
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/e2e-tests/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/faq/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/how-it-works/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/kubectl-plugin/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/lua_tests/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/troubleshooting/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/deploy/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/deploy/baremetal/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/deploy/hardening-guide/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/deploy/rbac/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/deploy/upgrade/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/developer-guide/code-overview/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/developer-guide/getting-started/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/enhancements/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/enhancements/20190724-only-dynamic-ssl/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/enhancements/20190815-zone-aware-routing/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/enhancements/20231001-split-containers/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/enhancements/YYYYMMDD-kep-template/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/PREREQUISITES/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/affinity/cookie/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/auth/basic/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/auth/client-certs/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/auth/external-auth/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/auth/oauth-external-auth/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/canary/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/customization/configuration-snippets/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/customization/custom-configuration/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/customization/custom-errors/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/customization/custom-headers/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/customization/external-auth-headers/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/customization/jwt/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/customization/ssl-dh-param/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/customization/sysctl/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/docker-registry/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/grpc/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/multi-tls/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/openpolicyagent/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/rewrite/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/static-ip/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/examples/tls-termination/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/basic-usage/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/cli-arguments/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/custom-errors/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/default-backend/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/external-articles/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/fcgi-services/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/ingress-path-matching/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/k8s-122-migration/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/miscellaneous/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/monitoring/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/multiple-ingress/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/tls/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations-risk/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/custom-template/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/log-format/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/third-party-addons/modsecurity/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://kubernetes.github.io/ingress-nginx/user-guide/third-party-addons/opentelemetry/</loc>
|
||||
<lastmod>2024-12-25</lastmod>
|
||||
<lastmod>2025-01-03</lastmod>
|
||||
<changefreq>daily</changefreq>
|
||||
</url>
|
||||
</urlset>
|
||||
BIN
sitemap.xml.gz
BIN
sitemap.xml.gz
Binary file not shown.
Loading…
Reference in a new issue