Skip to content

Releases: giantswarm/aws-resolver-rules-operator

v0.6.0

05 May 07:00
77148e2
Compare
Choose a tag to compare

Fixed

  • Use resource share status as filter when deleting RAM resource shares.
  • Change reconcilation logic to process existing RAM resource shares.

v0.5.0

19 Apr 13:39
3cc60c6
Compare
Choose a tag to compare

Changed

  • Change default registry in Helm chart from quay.io to docker.io.

v0.4.1

21 Mar 05:39
04ca052
Compare
Choose a tag to compare

Added

  • Add the use of runtime/default seccomp profile. Allow required volume types in PSP.

v0.4.0

15 Mar 09:51
8fd1d63
Compare
Choose a tag to compare

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

22 Feb 09:15
921c58e
Compare
Choose a tag to compare

Changed

  • Update golang.org/x/net to v0.7.0.

v0.2.1

08 Feb 10:17
68ea9ce
Compare
Choose a tag to compare

Fix

  • Revert seccomp profile.

v0.2.0

08 Feb 09:38
fa74bd8
Compare
Choose a tag to compare

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

24 Jan 12:44
50b775a
Compare
Choose a tag to compare

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

24 Jan 10:55
79314d1
Compare
Choose a tag to compare

Added

  • Initial implementation.

v0.0.1

20 Dec 09:02
c69abd2
Compare
Choose a tag to compare
  • changed: app.giantswarm.io label group was changed to application.giantswarm.io