Skip to content

CFE-72: make infrastructure resource tags updatable#685

Closed
Elbehery wants to merge 1 commit intoopenshift:masterfrom
Elbehery:make-aws-tags-updatable
Closed

CFE-72: make infrastructure resource tags updatable#685
Elbehery wants to merge 1 commit intoopenshift:masterfrom
Elbehery:make-aws-tags-updatable

Conversation

@Elbehery
Copy link
Copy Markdown

This PR adds a watch for Infrastructure type to update AWS tags when changed

@Elbehery
Copy link
Copy Markdown
Author

/assign @arjunrn
/assign @lmzuccarelli

@Elbehery
Copy link
Copy Markdown
Author

/retest

1 similar comment
@Elbehery
Copy link
Copy Markdown
Author

/retest

@Elbehery
Copy link
Copy Markdown
Author

This error exists on the master branch, not from my commit

@arjunrn
@lmzuccarelli
@Connect2naga

if err := c.Watch(&source.Kind{Type: &configv1.Ingress{}}, handler.EnqueueRequestsFromMapFunc(reconciler.ingressConfigToIngressController)); err != nil {
return nil, err
}
if err := c.Watch(&source.Kind{Type: &configv1.Infrastructure{}}, handler.EnqueueRequestsFromMapFunc(reconciler.ingressConfigToIngressController)); err != nil {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nice simple change

@lmzuccarelli
Copy link
Copy Markdown
Contributor

@Elbehery Can you check why the verify job is failing.

@Elbehery
Copy link
Copy Markdown
Author

@Elbehery Can you check why the verify job is failing.

there is a fix here openshift/build-machinery-go#58 .. I will try to bump in the machinary version in this repo

@Elbehery
Copy link
Copy Markdown
Author

@lmzuccarelli added this PR #688 to fix the issue

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 14, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Elbehery
To complete the pull request process, please ask for approval from lmzuccarelli after the PR has been reviewed.

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

Details 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

@Elbehery Elbehery force-pushed the make-aws-tags-updatable branch 3 times, most recently from d3988aa to 77c016c Compare December 14, 2021 16:35
awsLBHealthCheckIntervalAnnotation,
GCPGlobalAccessAnnotation,
localWithFallbackAnnotation,
awsLBAdditionalResourceTags,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This will cause the operator to override user changes to the annotation. @frobware, is there a reason the operator didn't manage this annotation before? Is documenting the change sufficient, or do we need to backport some logic to set Upgradeable=False if the user has set an annotation that doesn't match the tags specified in the infrastructure config?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

is there a reason the operator didn't manage this annotation before?

It's not clear to me whether this should have been specified previously or is/was a glaring omission; that's perhaps not terribly helpful but if we go ahead with this change then we should also go with the additional logic (and backports) for smooth upgrades (IMO).

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

@Miciah @frobware thanks a lot for your review

The target of this PR is a watch the AWS resource tags on the infrastructure crd and update the tags accordingly.
Would this change be sufficient for this purpose ?

cc @arjunrn @lmzuccarelli

@Elbehery
Copy link
Copy Markdown
Author

/retest

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 16, 2021
@Elbehery
Copy link
Copy Markdown
Author

/retest

@Elbehery Elbehery force-pushed the make-aws-tags-updatable branch from 77c016c to 1270adc Compare December 23, 2021 08:40
@openshift-ci openshift-ci Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 23, 2021
@Elbehery
Copy link
Copy Markdown
Author

/retest

1 similar comment
@Elbehery
Copy link
Copy Markdown
Author

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 23, 2021

@Elbehery: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jan 23, 2022

@Elbehery: PR needs rebase.

Details

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.

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 23, 2022
@openshift-bot
Copy link
Copy Markdown
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 23, 2022
@openshift-bot
Copy link
Copy Markdown
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 23, 2022
@openshift-bot
Copy link
Copy Markdown
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci Bot closed this Jun 22, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 22, 2022

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants