forked from openshift/api
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
route/v1: Fix CRD to allow path for non-TLS routes
Fix the Route CRD validation for allow routes with null spec.tls and nonempty spec.path. This commit is related to USHIFT-333. https://issues.redhat.com/browse/USHIFT-333 * route/v1/route.crd.yaml-patch: Add a case to allow spec.path to be nonempty when spec.tls is null. The existing case to allow spec.path when spec.tls.termination is not "passthrough" is insufficient when spec.tls is not specified at all. * route/v1/route.crd.yaml: Regenerate. * route/v1/test-route-validation.sh: Add test cases "non-TLS with nonempty path" and "edge-terminated with nonempty path".
- Loading branch information
Showing
3 changed files
with
40 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -69,6 +69,10 @@ spec: | |
- properties: | ||
path: | ||
maxLength: 0 | ||
- properties: | ||
tls: | ||
enum: | ||
- null | ||
- not: | ||
properties: | ||
tls: | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,6 +6,9 @@ | |
- properties: | ||
path: | ||
maxLength: 0 | ||
- properties: | ||
tls: | ||
enum: [null] | ||
- not: | ||
properties: | ||
tls: | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters