-
Notifications
You must be signed in to change notification settings - Fork 629
fix: propagate AdditionalTags from AWSCluster to storage volumes #4512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: propagate AdditionalTags from AWSCluster to storage volumes #4512
Conversation
Welcome @philjb! |
Hi @philjb. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
addressed in recent commits |
/ok-to-test |
/kind bug |
/retest |
@Skarlso - back to you whenever you have time. I addressed the test failures. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, I don't see any other places that use AWSMachine.Spec.AdditionalTags
that needs changing.
I didn't either. It's just that reconcile method that touches tags for the instance and root volumes as far as i saw. |
/test ? |
@Skarlso: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test pull-cluster-api-provider-aws-e2e-blocking |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Skarlso The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold |
thanks! |
annotations[volumeID] = newAnnotation | ||
} else { | ||
newAnnotation, err := r.ensureVolumeTags(ec2svc, aws.String(volumeID), make(map[string]interface{}), machine.Spec.AdditionalTags) | ||
newAnnotation, err := r.ensureVolumeTags(ec2svc, aws.String(volumeID), make(map[string]interface{}), additionalTags) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this line change didn't make it into 2.2.4 release through https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4535/files
Fix the backport of #4512 into release-2.2 branch
…altags-root-volumes fix: propagate AdditionalTags from AWSCluster to storage volumes
…altags-root-volumes fix: propagate AdditionalTags from AWSCluster to storage volumes
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR gets AWSCluster AdditionalTags onto root volumes for the AWSMachines in the cluster. I believe this is the intended behavior: Set the additional tags on the cluster and have them show up on all resources for that cluster.
I believe it was a minor oversight that the current behavior isn't like this already.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #4511
Special notes for your reviewer:
None
Checklist:
Release note: