search

aws / aws-app-mesh-controller-for-k8s

A controller to help manage App Mesh resources for a Kubernetes cluster.
Apache License 2.0
187 stars 109 forks source link

Improve experience when CloudMap Namespace doesn't exist #109

Open nckturner opened 4 years ago

nckturner commented 4 years ago

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.

kiranmeduri commented 4 years ago

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.

nckturner commented 4 years ago

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.

shubharao commented 4 years ago

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 commented 4 years ago

@achevuru is going to work on this issue.

astrived commented 4 years ago

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

RafalMaleska commented 3 years ago

are You planning to provide CloudMap as CRD?