Releases: giantswarm/aws-resolver-rules-operator
Releases · giantswarm/aws-resolver-rules-operator
v0.6.0
Fixed
- Use resource share status as filter when deleting RAM resource shares.
- Change reconcilation logic to process existing RAM resource shares.
v0.5.0
Changed
- Change default registry in Helm chart from quay.io to docker.io.
v0.4.1
Added
- Add the use of runtime/default seccomp profile. Allow required volume types in PSP.
v0.4.0
Added
- Add condition to
AWSCluster
signaling that resolver rules in AWS account have been associated with workload cluster VPC. - Add new reconciler that unpauses the
AWSCluster
CR when VPC, Subnets and Resolver Rules conditions are marked as ready.
v0.3.0
Changed
- Update
golang.org/x/net
to v0.7.0.
v0.2.1
Fix
- Revert seccomp profile.
v0.2.0
Added
- Associate existing Resolver Rules with workload cluster VPC.
- Add the use of runtime/default seccomp profile.
- Improve logging.
Fixed
- Don't create RAM resource share if it's already created.
- When creating the Resolver endpoints, only create it for the subnets with a specific tag on them.
v0.1.1
Fixed
- Don't try to find resolver rules associations filtering by association name, but only use resolver rule id and vpc id.
v0.1.0
Added
- Initial implementation.
v0.0.1
- changed:
app.giantswarm.io
label group was changed toapplication.giantswarm.io