@@ -165,8 +165,8 @@ default on the next breaking change release, set for 2.0.0.
165
165
166
166
- When "` ingress.spec.rules.http.pathType=Exact ` " or "` pathType=Prefix ` ", this
167
167
validation 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 " ` / ` ".
170
170
171
171
- When the ingress resource path contains other characters (like on rewrite
172
172
configurations), the pathType value should be "` ImplementationSpecific ` ".
@@ -175,7 +175,7 @@ configurations), the pathType value should be "`ImplementationSpecific`".
175
175
176
176
- When this option is enabled, the validation will happen on the Admission
177
177
Webhook. 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
179
179
is not using ` pathType ` value as ` ImplementationSpecific ` , then the ingress
180
180
object will be denied admission.
181
181
0 commit comments