v0.3.0
What's Changed
- Added managed by label - issue 110 by @matthewgoodman13 in #139
- Implement end-to-end EKS integration test by @fredjywang in #154
- Update libs to support Apple silicon by @astaticvoid in #164
- Propagate ClusterID to Cloud Map & Endpoints by @matthewgoodman13 in #165
- Importing Headless Services Support for A/AAAA records by @fredjywang in #180
- New DerivedServices Architecture + Source-Cluster label by @matthewgoodman13 in #179
- Headless services local integration test by @fredjywang in #194
- Add support for Ready, Hostname and Nodename Endpoint attributes. And some other refactoring changes. by @runakash in #210
- Add User-Agent by @runakash in #215
- Update the ClusterProperty id.k8s.io by @runakash in #221
New Contributors
- @fredjywang made their first contribution in #132
- @matthewgoodman13 made their first contribution in #139
Full Changelog: v0.2.3...v0.3.0
Upgrading from v0.2.x
Delete the previous release from each cluster.
kubectl delete -k "github.com/aws/aws-cloud-map-mcs-controller-for-k8s/config/controller_install_release?ref=v0.2.0"
The endpoint schema which the controller exports to AWS Cloud Map has changed, and will have to be rebuilt. You can clear out the registered endpoints using the integration test janitor script.
go run ./integration/janitor/runner/main.go $NAMESPACE
Warning: This will de-register all service instances and delete all services under $NAMESPACE in AWS Cloud Map, and then delete the namespace as well. It will not modify anything in the cluster. Running the controller will then re-export your services.