no TLS port found on ingress gateway

[rvennam]

This warning can happen if the users ingress-gateway does not have the TLS port that gloo mesh needs for east-west traffic between clusters. This port will not be there on default ingress gateways ... users need to follow our documentation to configure the gateway for east west mullticluster. https://docs.solo.io/gloo-mesh/latest/setup/gloo_mesh_istio/

This warning should be re-written to something more user friendly, such as - "Istio Ingress Gateway is missing the tls port required for multicluster communication"

│ {"level":"warn","ts":1625589542.3642917,"logger":"reconcile-23.detector","msg":"detection failed for matching istio ingress service","error":"no TLS port found on ingress gateway","errorVerbose":"no TLS port found on ing │
│ ress gateway\n\tinput.(*inputReconciler).processNextWorkItem:/home/runner/go/pkg/mod/github.com/solo-io/[email protected]/contrib/pkg/input/input_reconciler.go:137\n\treconciliation.(*discoveryReconciler).reconcileLocal:/hom │
│ e/runner/go/pkg/mod/github.com/solo-io/[email protected]/pkg/mesh-discovery/reconciliation/discovery_reconciler.go:145\n\treconciliation.(*discoveryReconciler).reconcile:/home/runner/go/pkg/mod/github.com/solo-io/g │
│ [email protected]/pkg/mesh-discovery/reconciliation/discovery_reconciler.go:185\n\ttranslation.translator.Translate:/home/runner/go/pkg/mod/github.com/solo-io/[email protected]/pkg/mesh-discovery/translation/d │
│ iscovery_translator.go:49\n\tmesh.(*translator).TranslateMeshes:/home/runner/go/pkg/mod/github.com/solo-io/[email protected]/pkg/mesh-