Tags: aws-controllers-k8s/runtime
Tags
fix: ensure Status fields are populated! (#181) Issue [#2459](aws-controllers-k8s/community#2459) Description of changes: When we have adopt-or-create, the populated status was not getting patched to k8s. So, during the next reconcile, the controller attempts to recreate the resource. With this fix, we ensure that the controller does patch the resource with the adoption field! By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
update: Update the `Resource already exists` condition reason (#177) Description of changes: Currently the condition reason for the `Resource Already Exists` condition message instructs users to adopt the existing resource using the `AdoptResource` CRD, which we no longer implement. This change updates the message to instruct users to instead use the adoption by annotation feature to import an existing resource. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
feat(tags): filter AWS tags and ACK tags during reconciliation (#170) * feat(tags): add SyncAWSTags for AWS-managed tag preservation Add utility to automatically preserve immutable AWS-managed tags (aws:*) when modifying resources. Prevents tag operation errors with CloudFormation and Service Catalog managed resources. * Add FilterAWSTags as a method in AWSResourceManager interface. This funtion will filter out tags injected by AWS and ACK.
PreviousNext