Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
README.md | 2022-12-09 | 1.7 kB | |
v0.3.1.tar.gz | 2022-12-09 | 529.2 kB | |
v0.3.1.zip | 2022-12-09 | 603.3 kB | |
Totals: 3 Items | 1.1 MB | 0 |
What's Changed
- API Rate Limiter by @runakash in https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/pull/243
- Explicit error handling by @runakash in https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/pull/244
- Rework operation poller by @runakash in https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/pull/245
- Add deletecollection verb. by @runakash in https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/pull/248
- Check cluster ID during service export by @bansal19 in https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/pull/255
- Step by step guide by @cameronsenese
New Contributors
- @bansal19 made their first contribution in https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/pull/252
Full Changelog: https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/compare/v0.3.0...v0.3.1
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_NAME
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.