Skip to content

Conversation

@mfojtik
Copy link

@mfojtik mfojtik commented Feb 10, 2022

When an external actor modifies the clusteroperators/ingress resource, it takes 10h[1] for the ingress operator to react and reconcile.
This fix (hopefully) makes the ingress operator reconcile the status when clusteroperator resource change, so it should react to any modification immediately.

[1] https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/manager#example-New

@openshift-ci openshift-ci bot requested review from candita and miheer February 10, 2022 12:22
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mfojtik
To complete the pull request process, please assign miciah after the PR has been reviewed.
You can assign the PR to them by writing /assign @miciah in a comment when ready.

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

Comment on lines +68 to +70
if err := c.Watch(&source.Kind{Type: &configv1.ClusterOperator{}}, &handler.EnqueueRequestForObject{}); err != nil {
return nil, err
}
Copy link
Contributor

Choose a reason for hiding this comment

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

We only care about the ingress clusteroperator, and the reconciler reconciles ingresscontrollers, so this new watch should filter clusteroperators by name and then enqueue an ingresscontroller object (the default ingresscontroller should always exist, so we could use that) rather than the clusteroperator object to so as to maintain a homogeneous workqueue (reconciling the ingresscontroller will ultimately update or recreate the clusteroperator as needed).

We did something similar for the cluster-dns-operator a while back: openshift/cluster-dns-operator#261

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2022

@mfojtik: The following tests 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 70a4710 link true /test e2e-aws
ci/prow/e2e-upgrade 70a4710 link true /test e2e-upgrade
ci/prow/e2e-gcp-serial 70a4710 link true /test e2e-gcp-serial
ci/prow/e2e-aws-single-node 70a4710 link false /test e2e-aws-single-node
ci/prow/e2e-aws-operator 70a4710 link true /test e2e-aws-operator

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.

@Miciah
Copy link
Contributor

Miciah commented Mar 3, 2022

/close
Superseded by #714.

@openshift-ci openshift-ci bot closed this Mar 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2022

@Miciah: Closed this PR.

Details

In response to this:

/close
Superseded by #714.

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants