Improve experience when CloudMap Namespace doesn't exist

[aws]

Improve experience when CloudMap Namespace doesn't exist

[nckturner]

Yes, I think we should either work towards deprecating the mesh resource and expect users to create them out of band, or allow a single cluster to own the mesh and cloudmap namespaces.

[kiranmeduri]

I am against this given namespace can be of scope larger than a single Kubernetes cluster. One can argue the same for mesh CRD but we already added it. Specifically this can be a problem when there are services in same namespace that are deployed in different clusters or across compute platforms. Open to discuss this further.

[shubharao]

Investigate: should mesh creation take an input on "also create a namespace"
Investigate: should app mesh entities be auto-created to map to existing K8s resources - cluster name, namespace name, services etc.

[astrived]

@achevuru is going to work on this issue.

[astrived]

This is working as designed, we will revisit this ask based on customer feedback.

[RafalMaleska]

are You planning to provide CloudMap as CRD?