CFE-72: make infrastructure resource tags updatable#685
CFE-72: make infrastructure resource tags updatable#685Elbehery wants to merge 1 commit intoopenshift:masterfrom
Conversation
|
/assign @arjunrn |
|
/retest |
1 similar comment
|
/retest |
|
This error exists on the master branch, not from my commit |
| 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 { |
|
@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 |
|
@lmzuccarelli added this PR #688 to fix the issue |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Elbehery The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
d3988aa to
77c016c
Compare
| awsLBHealthCheckIntervalAnnotation, | ||
| GCPGlobalAccessAnnotation, | ||
| localWithFallbackAnnotation, | ||
| awsLBAdditionalResourceTags, |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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).
|
/retest |
|
/retest |
77c016c to
1270adc
Compare
|
/retest |
1 similar comment
|
/retest |
|
@Elbehery: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
@Elbehery: PR needs rebase. DetailsInstructions 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. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. DetailsIn 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. |
This PR adds a watch for Infrastructure type to update AWS tags when changed