Skip to content

Conversation

@a-hilaly
Copy link
Member

When resources are managed by KRO, ACK now includes KRO information in
AWS API calls through user agent strings and resource tags. This makes
it easier to understand which resources came from KRO when looking at
AWS CloudTrail logs, cost allocation reports, and usage metrics. The
implementation detects KRO managed resources via the standard Kubernetes
app.kubernetes.io/managed-by label (with backward compatibility for the
legacy kro.run/owned label), and adds optional %MANAGED_BY% and
%KRO_VERSION% tag formats that can be used in default tags configuration.
Empty tag values are automatically skipped to keep resources clean.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ack-prow ack-prow bot requested review from knottnt and michaelhtm November 23, 2025 04:12
@ack-prow ack-prow bot added the approved label Nov 23, 2025
@a-hilaly a-hilaly changed the title feat(runtime): add KRO context to user agent and tags feat(runtime): add k8s-managed-by and kro version context to user agent and tags Nov 23, 2025
When resources are managed by KRO, ACK now includes KRO information in
AWS API calls through user agent strings and resource tags. This makes
it easier to understand which resources came from KRO when looking at
AWS CloudTrail logs, cost allocation reports, and usage metrics. The
implementation detects KRO managed resources via the standard Kubernetes
`app.kubernetes.io/managed-by` label (with backward compatibility for the
legacy `kro.run/owned` label), and adds optional `%MANAGED_BY%` and
`%KRO_VERSION%` tag formats that can be used in default tags configuration.
Empty tag values are automatically skipped to keep resources clean.
Copy link
Member

@michaelhtm michaelhtm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@ack-prow ack-prow bot added the lgtm Indicates that a PR is ready to be merged. label Nov 23, 2025
@ack-prow
Copy link

ack-prow bot commented Nov 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: a-hilaly, michaelhtm

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:
  • OWNERS [a-hilaly,michaelhtm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ack-prow
Copy link

ack-prow bot commented Nov 23, 2025

@a-hilaly: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
verify-attribution 5fa3a2b link false /test verify-attribution

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@a-hilaly
Copy link
Member Author

/test s3-controller-test

@michaelhtm michaelhtm merged commit db66fa4 into aws-controllers-k8s:main Nov 23, 2025
5 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants