From f84f5cc81d741e3d7325f5612ab34d0ee21b3a1e Mon Sep 17 00:00:00 2001 From: k8s-ci-robot Date: Mon, 18 Sep 2023 15:29:35 +0000 Subject: [PATCH] Deploy GitHub Pages --- examples/rewrite/index.html | 2 +- sitemap.xml.gz | Bin 741 -> 741 bytes 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/rewrite/index.html b/examples/rewrite/index.html index 6f469feb3..bdfed4d68 100644 --- a/examples/rewrite/index.html +++ b/examples/rewrite/index.html @@ -1,4 +1,4 @@ - Rewrite - Ingress-Nginx Controller
Skip to content

Rewrite

This example demonstrates how to use Rewrite annotations.

Prerequisites

You will need to make sure your Ingress targets exactly one Ingress controller by specifying the ingress.class annotation, and that you have an ingress controller running in your cluster.

Deployment

Rewriting can be controlled using the following annotations:

Name Description Values
nginx.ingress.kubernetes.io/rewrite-target Target URI where the traffic must be redirected string
nginx.ingress.kubernetes.io/ssl-redirect Indicates if the location section is only accessible via SSL (defaults to True when Ingress contains a Certificate) bool
nginx.ingress.kubernetes.io/force-ssl-redirect Forces the redirection to HTTPS even if the Ingress is not TLS Enabled bool
nginx.ingress.kubernetes.io/app-root Defines the Application Root that the Controller must redirect if it's in / context string
nginx.ingress.kubernetes.io/use-regex Indicates if the paths defined on an Ingress use regular expressions bool

Examples

Rewrite Target

Attention

Starting in Version 0.22.0, ingress definitions using the annotation nginx.ingress.kubernetes.io/rewrite-target are not backwards compatible with previous versions. In Version 0.22.0 and beyond, any substrings within the request URI that need to be passed to the rewritten path must explicitly be defined in a capture group.

Note

Captured groups are saved in numbered placeholders, chronologically, in the form $1, $2 ... $n. These placeholders can be used as parameters in the rewrite-target annotation.

Note

Please see the FAQ for Validation Of path

Create an Ingress rule with a rewrite annotation:

$ echo '
+ Rewrite - Ingress-Nginx Controller      
 
 
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
    
Rewrite
 
This example demonstrates how to use Rewrite annotations.
 
Prerequisites
 
You will need to make sure your Ingress targets exactly one Ingress controller by specifying the ingress.class annotation, and that you have an ingress controller running in your cluster.
 
Deployment
 
Rewriting can be controlled using the following annotations:
 
  
 Name Description Values 
   
 nginx.ingress.kubernetes.io/rewrite-target Target URI where the traffic must be redirected string 
 
 nginx.ingress.kubernetes.io/ssl-redirect Indicates if the location section is only accessible via SSL (defaults to True when Ingress contains a Certificate) bool 
 
 nginx.ingress.kubernetes.io/force-ssl-redirect Forces the redirection to HTTPS even if the Ingress is not TLS Enabled bool 
 
 nginx.ingress.kubernetes.io/app-root Defines the Application Root that the Controller must redirect if it's in / context string 
 
 nginx.ingress.kubernetes.io/use-regex Indicates if the paths defined on an Ingress use regular expressions bool 
  
 
Examples
 
Rewrite Target
 
 
Attention
 
Starting in Version 0.22.0, ingress definitions using the annotation nginx.ingress.kubernetes.io/rewrite-target are not backwards compatible with previous versions. In Version 0.22.0 and beyond, any substrings within the request URI that need to be passed to the rewritten path must explicitly be defined in a capture group.
 
 
 
Note
 
Captured groups are saved in numbered placeholders, chronologically, in the form $1, $2 ... $n. These placeholders can be used as parameters in the rewrite-target annotation.
 
 
 
Note
 
Please see the FAQ for Validation Of path
 
 
Create an Ingress rule with a rewrite annotation:
 
$ echo '
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index 09a929d656ac8017355d385b2f00d664f08ba8b1..0922a0c1ad46731b0196cc41747fa29099843fea 100644
GIT binary patch
delta 15
WcmaFL`jnMTzMF&NcFsn&`%C~VL