-
Notifications
You must be signed in to change notification settings - Fork 0
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
Expose additionalTags
value from CAPA in cluster-aws
and cluster-eks
#2929
Comments
TODO
|
S3 buckets for ignition are not tagged in the latest CAPA controller release, I was checking the code and found out that @AndiDog actually implemented it :p wow so the last part is blocked by upstream release |
I'll try to cherry-pick the S3 tagging change into our fork |
unfortunately, the changes in capa-controller only add basic tags
but do not add tags under
that means customer tags are not applied, this will need to be fixed in the capa controller |
I'll take care of |
Fixed in kubernetes-sigs/cluster-api-provider-aws#4625 and I'll cherry-pick it immediately into our fork because it's so straightforward and unlikely that the PR content changes. |
LGTM |
Based on the CAPA implementation: kubernetes-sigs/cluster-api-provider-aws#1113
We should be able to expose
additionalTags
value in ourcluster-aws
andcluster-eks
for tagging the AWS Resources. This feature is highly wanted by customers either for cost tracking or security processes.Initial implementation should consider the population of the tags during creation of clusters only, however besides CAPI controllers we have to extend population of the tags also within our custom controllers.
The text was updated successfully, but these errors were encountered: