Skip to content
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

CFE-1133: Watch Infrastructure and update AWS tags #137

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

chiragkyal
Copy link
Member

@chiragkyal chiragkyal commented Sep 24, 2024

This PR adds support for AWS user tags specified in the platform status. Tags can be managed centrally in the PlatformStatus and have them automatically applied to resources managed by the ALBC.

  • Adds a watch on the Infrastructure object to detect changes in the platformStatus.AWS.ResourceTags field.
  • Merges tags from both the AWSLoadBalancerController.Spec.AdditionalResourceTags and the PlatformStatus.AWS.ResourceTags into a single list, prioritizing tags from the operator spec.
  • Ensures that the combined tag list does not exceed the maximum allowed limit of 24 tags for the ALBC's --default-tags argument.

Implements CFE-1133

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 24, 2024

@chiragkyal: This pull request references CFE-1133 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 24, 2024
Copy link
Contributor

openshift-ci bot commented Sep 24, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign alebedev87 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

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

@chiragkyal chiragkyal force-pushed the aws-tags branch 3 times, most recently from 3d5641f to f413d74 Compare September 25, 2024 09:29
@chiragkyal
Copy link
Member Author

/test images

@chiragkyal
Copy link
Member Author

/retest-required

@chiragkyal
Copy link
Member Author

/test all

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 30, 2024

@chiragkyal: This pull request references CFE-1133 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

This PR adds support for AWS user tags specified in the platform status. Tags can be managed centrally in the PlatformStatus and have them automatically applied to resources managed by the ALBC.

  • Adds a watch on the Infrastructure object to detect changes in the platformStatus.AWS.ResourceTags field.
  • Merges tags from both the AWSLoadBalancerController.Spec.AdditionalResourceTags and the PlatformStatus.AWS.ResourceTags into a single list, prioritizing tags from the operator spec.
  • Ensures that the combined tag list does not exceed the maximum allowed limit of 24 tags for the ALBC's --default-tags argument.

Implements CFE-1133

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 openshift-eng/jira-lifecycle-plugin repository.

@chiragkyal chiragkyal changed the title CFE-1133: [WIP] Watch infrastructure and update AWS tags CFE-1133: Watch Infrastructure and update AWS tags Sep 30, 2024
@chiragkyal chiragkyal force-pushed the aws-tags branch 2 times, most recently from c177a9c to 48c649a Compare October 1, 2024 06:34
@chiragkyal
Copy link
Member Author

/retest-required

- Added watch on Infrastructure object to detect changes in PlatformStatus.AWS.ResourceTags.
- Merged tags from AWSLoadBalancerController.Spec.AdditionalResourceTags and PlatformStatus.AWS.ResourceTags, prioritizing operator spec tags.

Signed-off-by: chiragkyal <ckyal@redhat.com>
@chiragkyal
Copy link
Member Author

/retest

Signed-off-by: chiragkyal <ckyal@redhat.com>
@chiragkyal
Copy link
Member Author

/assign @alebedev87

@chiragkyal
Copy link
Member Author

/retest

Copy link
Contributor

openshift-ci bot commented Oct 17, 2024

@chiragkyal: 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
ci/prow/e2e-aws-rosa-operator 1879fb2 link true /test e2e-aws-rosa-operator

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants