-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.13.0
-
None
-
False
-
-
NA
Description of problem:
On clusters serving Route via CRD (i.e. MicroShift), .spec.host values are not automatically assigned during Route creation, as they are on OCP.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
$ cat<<EOF | oc apply --server-side -f- apiVersion: route.openshift.io/v1 kind: Route metadata: name: hello-microshift spec: to: kind: Service name: hello-microshift EOF route.route.openshift.io/hello-microshift serverside-applied $ oc get route hello-microshift -o yaml apiVersion: route.openshift.io/v1 kind: Route metadata: annotations: openshift.io/host.generated: "true" creationTimestamp: "2022-11-11T23:53:33Z" generation: 1 name: hello-microshift namespace: default resourceVersion: "2659" uid: cd35cd20-b3fd-4d50-9912-f34b3935acfd spec: host: hello-microshift-default.cluster.local to: kind: Service name: hello-microshift wildcardPolicy: None
Expected results:
... metadata: annotations: openshift.io/host.generated: "true" ... spec: host: hello-microshift-default.foo.bar.baz ...
Actual results:
Host and host.generated annotation are missing.
Additional info:
** This change will be inert on OCP, which already has the correct behavior. **
- blocks
-
OCPBUGS-3833 Route CRD host-assignment behavior must be the same as openshift-apiserver behavior
- Closed
-
OCPBUGS-3875 Route CRD host-assignment behavior must be the same as openshift-apiserver behavior
- Closed
- is blocked by
-
OCPBUGS-3502 CRD-based and openshift-apiserver-based Route validation/defaulting must use the shared implementation
- Closed
- is cloned by
-
OCPBUGS-3875 Route CRD host-assignment behavior must be the same as openshift-apiserver behavior
- Closed
- relates to
-
OCPBUGS-3499 Route CRD validation behavior must be the same as openshift-apiserver behavior
- Closed
- links to