-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.10.z
-
None
Description of problem:
Command `$ oc explain route.spec.tls.insecureEdgeTerminationPolicy` shows different values than the actual values.
Version-Release number of selected component (if applicable):
4.10.z
How reproducible:
100%
Steps to Reproduce:
1. $ oc explain route.spec.tls.insecureEdgeTerminationPolicy
KIND: Route
VERSION: route.openshift.io/v1FIELD: insecureEdgeTerminationPolicy <string>DESCRIPTION:
insecureEdgeTerminationPolicy indicates the desired behavior for insecure
connections to a route. While each router may make its own decisions on
which ports to expose, this is normally port 80.
* Allow - traffic is sent to the server on the insecure port (default)
* Disable - no traffic is allowed on the insecure port.
* Redirect - clients are redirected to the secure port.
2. Set the option to 'Disable' in any secure route :
$ oc edit route <route-name>
spec:
host: hello.example.com
port:
targetPort: https
tls:
insecureEdgeTerminationPolicy: Disable
3. After editing the route and setting `insecureEdgeTerminationPolicy: Disable` , it gives error :
Danger alert:An error occurred
Error "Invalid value: "Disable": invalid value for InsecureEdgeTerminationPolicy option, acceptable values are None, Allow, Redirect, or empty" for field "spec.tls.insecureEdgeTerminationPolicy".
Actual results:
Based on the API Usage information, the Disable value for insecureEdgeTerminationPolicy field is not acceptable.
Expected results:
The `oc explain route.spec.tls.insecureEdgeTerminationPolicy` must show the correct values.
Additional info:
