Route CRD vs. OCP defaulting disparity

Certain Route defaults behave differently on MicroShift (using the CR handler) vs. OCP. The behavior should be the same as on OCP.

Specifically:

- spec.to.kind should default to "Service" if it's specified by the client as ""
- spec.wildcardPolicy should default to "None" if it's specified by the client as ""
- spec.tls.termination should default to "edge" if it's specified by the client as "" AND spec.tls.destinationCACertificate is specified by the client as ""
- spec.tls.termination should default to "edge" if it's specified by the client as "Edge"
- spec.tls.termination should default to "reencrypt" if it's specified by the client as "Reencrypt"
- spec.tls.termination should default to "passthrough" if it's specified by the client as "Passthrough"

4.12

Always

$ cat <<EOF | oc apply -f-
apiVersion: route.openshift.io/v1
kind: Route
metadata:
  name: hello-microshift
spec:
  to:
    kind: "" 
    name: hello-microshift
EOF

$ oc get route hello-microshift -o yaml

The Route "hello-microshift" is invalid: spec.to.kind: Invalid value: "": must reference a Service

apiVersion: route.openshift.io/v1
kind: Route
metadata:
  name: hello-microshift
  namespace: default
spec:
  to:
    kind: Service

The CR handler only applies defaults to fields that are omitted from the request body, or, if the field is not nullable per the schema, are serialized as null. This is why the above Route is accepted when spec.to.kind is absent, but rejected when present, even when empty.