Akash Rungta

Initial implementation of the controller is purely focused on IPv4 support. Research if dual-stack support is needed and implement that. Dual stack networking is coming to K8s soon: `(alpha: "v1.20"/beta:...

Set `User-Agent` to the CloudMap API calls. This is going to help us track the API usages via MCS controller.

Right now, we are using the default configuration for reconciles. We can optimize the reconciler to improve performance. https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/controller#Options

Current strategy for error handling is to log the error. This story is figure out ways to extend error handling capabilities, and make the reconciler fault-tolerant.

Proper error handling during the startup for the non-recoverable states. For example: If we fail to sign request because of missing credentials, terminate the controller instead of retrying ``` failed...

As per the [Multi-Cluster Services API](https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/1645-multi-cluster-services-api#endpoint-ttl), we need to define the strategy for below > Endpoint TTL > > To prevent stale endpoints from persisting in the event that the...

Set aws-region via kustomize edit command instead of the environment variable substitution. Environmental substitution was a bug documented as a feature, and is going to be fixed in the future...

1. Configure 2 kind clusters, and ensure the controller features works across them 2. Inject AWS creds into the controlller docker as env variables 3. Use separate namespace for each...