1.6.1

• Fixed the ComputeInstance idempotency issue (#103)
• Other miscellaneous bug fixes and improvements

1.6.0

• Add "Deletion Defender" workload -- a pod whose job is to ensure that only resources meant to trigger a delete on the underlying API do so. If this workload goes down for whatever reason, the controller is prevented from performing deletions, thus protecting against accidental deletions for misconfigured instances of Config Connector.
• Add support for structured metadata list for ComputeInstance and ComputeInstanceTemplate in the form of a spec.metadata field.

1.5.2

• Fixed label update issue on ContainerCluster (#110)
• Bumped memory request and limit for the manager pod as resource usage has gone up and the original limit of 256 Mi was found to not be sufficient for large customers
• Changed admission webhooks to return non-200 error codes when denying admission

1.5.1

miscellaneous bug fixes and improvements

1.5.0

• ComputeHealthCheck's location field now supports supplying a region
• Fixed an issue with deleting StorageBucketAccessControl when the ServiceAccount did not exist: #39
• With the exception of role-bindings, moved all system components for namespaced mode into the cnrm-system, note: you must completely uninstall and reinstall to upgrade namespaced mode completely for this release.
• Added a version annotation to the Config Connector manifests

1.4.0

• added update support for the adminEnabled field in ComputeInterconnectAttachment
• added support for IAM Conditions for the following resources:
  • ComputeInstance
  • ComputeSubnetwork
  • IAMServiceAccount
  • KMSCryptoKey
  • KMSKeyRing
  • Project
  • Folder
  • StorageBucket

1.3.1

• Added a mechanism to prevent Config Connector from managing the same resource across multiple namespaces.

  • You can control this behavior by specifying an annotation of cnrm.cloud.google.com/management-conflict-prevention-policy on your resource config with one of the following values:

    • resource: management conflicts are prevented at the resource level by saving the appropriate lease labels into the resource.
    • none: management conflicts are not prevented.

    The default value is chosen as follows: resource if the GCP resource supports labels; otherwise, none.

1.3.0

• Added support for DataflowJob
• bug fixes

1.2.0

• Added support for ComputeNetworkEndpointGroup
• Fixed the issue about unable to delete the IAMPolicy if the referenced resource is deleted first

1.1.1

• added support for DNSPolicy
• miscellaneous bug fixes