@@ -165,8 +165,8 @@ default on the next breaking change release, set for 2.0.0.
165165
166166- When "` ingress.spec.rules.http.pathType=Exact ` " or "` pathType=Prefix ` ", this
167167validation will limit the characters accepted on the field "` ingress.spec.rules.http.paths.path ` ",
168- to "` alphanumeric characters ` ", and ` "/," "_," "-." ` Also, in this case,
169- the path should start with ` "/." `
168+ to "` alphanumeric characters ` ", and " ` / ` ", " ` _ ` ", " ` - ` ". Also, in this case,
169+ the path should start with " ` / ` ".
170170
171171- When the ingress resource path contains other characters (like on rewrite
172172configurations), the pathType value should be "` ImplementationSpecific ` ".
@@ -175,7 +175,7 @@ configurations), the pathType value should be "`ImplementationSpecific`".
175175
176176- When this option is enabled, the validation will happen on the Admission
177177Webhook. So if any new ingress object contains characters other than
178- alphanumeric characters, and, ` "/,","_","-" ` , in the ` path ` field, but
178+ alphanumeric characters, and, " ` / ` ", " ` _ ` ", " ` - ` " , in the ` path ` field, but
179179is not using ` pathType ` value as ` ImplementationSpecific ` , then the ingress
180180object will be denied admission.
181181
0 commit comments