Akash Rungta

We released new version which should improve with the api throttling https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/releases/tag/v0.3.1 Feel free to let us know, if any new errors are encountered.

Hello Santosh - We can keep this ticket open and work on the future based on the prioritization. Meanwhile I can recommend building the arm64 based docker on your own....

Looks like you're logging the address to the struct.

Using `EndpointSlice` was a deliberate design choice to support large number of endpoints. And also is par with the Kubernetes's recommendation. > This will cause issues related to RollingUpdate, as...

> Does the MCS controller work only when pods in both clusters are in routable networks? The clusters need to be in the peered networks. And for peering to work...

Should be fixed by the https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/issues/254.

Hello [techmouse84](https://github.com/techmouse84) - We do not support Topology Aware Hints yet. Even [mcs spec](https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/1645-multi-cluster-services-api#constraints) references the deprecated Topology API. We can definitely have a look into integrating in future milestones.

Hello @mukshe01, We don't have support custom attributes export/import. > currently we are using a lambda trigger in aws to populate these custom attributes. this is causing an issue with...

You can use this reference to customize the logging https://sdk.operatorframework.io/docs/building-operators/golang/references/logging/

On reviewing the ServiceExport controller code, it seems we are exporting the endpoints based on the k8s events on the Service and EndpointSlice. Updating metadata will trigger the k8s events,...