-
Notifications
You must be signed in to change notification settings - Fork 33
Migrate controller to use function SetupWithManager #82
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
Migrate controller to use function SetupWithManager #82
Conversation
|
Not sure why deployment error is popping up now so will retry: /test operator-e2e |
|
Works locally but took ~7 minutes for operand deployment to be ready so perhaps it was too slow in coming up in Ci env. |
|
/test operator-e2e |
|
Have an issue to fix causing test failure /hold |
We should be pulling that from the CI registry... |
The outgoing docker.io image was subject to docker.io rate limiting [1]: error: build error: failed to pull image: After retrying 2 times, Pull image still failed due to error: while pulling "docker://docker.io/openshift/origin-release:golang-1.13" as "docker.io/openshift/origin-release:golang-1.13"... The new image matches openshift/cluster-version-operator@7cb2662924 (Updating cluster-version-operator builder & base images to be consistent with ART, 2020-10-07, openshift/cluster-version-operator#468). Matching builders with the CVO reduces our exposure by consolidating around a smaller set of Go builder images. [1]: openshift#82 (comment)
The outgoing docker.io image was subject to docker.io rate limiting [1]: error: build error: failed to pull image: After retrying 2 times, Pull image still failed due to error: while pulling "docker://docker.io/openshift/origin-release:golang-1.13" as "docker.io/openshift/origin-release:golang-1.13"... The new image matches openshift/cluster-version-operator@7cb2662924 (Updating cluster-version-operator builder & base images to be consistent with ART, 2020-10-07, openshift/cluster-version-operator#468). Matching builders with the CVO reduces our exposure by consolidating around a smaller set of Go builder images. I expect that after this lands, openshift/registry will pick it up via a change like openshift/release@d0fa1c98b9 (Registry-replacer autocommit, 2020-10-07, openshift/release#12532). [1]: openshift#82 (comment)
|
Needs a rebase as #86 is merged now. |
Supported legacy leader.Become method required operator-lib dependency.
7122c12 to
56104f6
Compare
56104f6 to
5caf9dc
Compare
LalatenduMohanty
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jottofar, LalatenduMohanty The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/unhold |
This was not originally done in the migration to operator-sdk v0.19.3. In that original migration I choose to continue using the legacy leader election method, which is still supported, and was not sure how to do so while also using SetupWithManager. This PR migrates leader election to the controller-runtime’s leader with lease mechanism as well.
Also added back in a couple of kubebuilder:scaffold markers which shouldn't have been deleted