-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
maistra-2.1.0
-
None
-
None
-
False
-
False
-
Undefined
-
While I was exploring mesh federation, I saw the following error:
Errors: * route/istio-system-federation-discovery-mesh2-ingress-525eca1d5089dbdc was not accepted by router "default": apps.mluksa-test1.servicemesh.devcluster.openshift.comhost name validation errors: spec.host: Invalid value: "istio-system-federation-discovery-mesh2-ingress-525eca1d5089dbdc-istio-system.apps.mluksa-test1.servicemesh.devcluster.openshift.com": must be no more than 63 characters (InvalidHost)
The oc get route command returned the following:
NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD federation-ingress federation-ingress-istio-system.apps.mluksa-test1.servicemesh.devcluster.openshift.com federation-ingress 8080 None istio-ingressgateway istio-ingressgateway-istio-system.apps.mluksa-test1.servicemesh.devcluster.openshift.com istio-ingressgateway 8080 None istio-system-federation-discovery-mesh2-egress-bdcbca3eddaf64c2 federation-egress.istio-system.svc.cluster.local federation-egress http2 None istio-system-federation-discovery-mesh2-ingress-525eca1d5089dbdc InvalidHost federation-ingress https passthrough None
It seems like we're generating very long route names.
- duplicates
-
MAISTRA-2375 ior attempts to create OCP route for federation gateways
- Closed