aws-app-mesh-controller-for-k8s icon indicating copy to clipboard operation
aws-app-mesh-controller-for-k8s copied to clipboard

Published 20 hours ago • verified publisher icon aws

Improve experience when CloudMap Namespace doesn't exist

Open nckturner opened this issue 6 years ago • 6 comments

Currently, the CloudMap Namespace has to be created out of band from the rest of the resources. There should be an automated way to create it, whether its a separate custom resource like the Mesh (which can be auto created by the injector) or something else.

nckturner avatar Nov 27 '19 22:11 nckturner

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.

kiranmeduri avatar Jan 15 '20 22:01 kiranmeduri

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.

nckturner avatar Jan 31 '20 23:01 nckturner

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.

shubharao avatar Feb 05 '20 21:02 shubharao

@achevuru is going to work on this issue.

astrived avatar Mar 04 '20 21:03 astrived

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

astrived avatar May 27 '20 20:05 astrived

are You planning to provide CloudMap as CRD?

RafalMaleska avatar Mar 09 '21 20:03 RafalMaleska