Move to the latest operator-sdk 1.26.0

[tkrishtop]

Signed-off-by: Tatiana Krishtop tkrishto@redhat.com

That should allow for getting more detailed error messages when the scorecard-sdk times out.

[openshift-ci]

Hi @tkrishtop. Thanks for your PR.

I'm waiting for a redhat-openshift-ecosystem member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[coveralls]

Coverage: 81.897%. Remained the same when pulling e12ab76 on tkrishtop:operator_sdk_1_26 into 8755b37 on redhat-openshift-ecosystem:main.

[dcibot]

• SUCCESS https://www.distributed-ci.io/jobs/58987a7e-8dba-4cc1-8ce2-8372136253b8/jobStates
  from Move to the latest operator-sdk 1.26.0 #864

[tkrishtop]

Regular contributors should join the org to skip this step.

Hi @acornett21, do you know who to ping to join?

[acornett21]

/ok-to-test

[acornett21]

@tkrishtop I'm not sure who owns the redhat-openshift-ecosystem org.

@jomkz Do you happen to know?

[bcrochet]

Would love to wait for this to land: operator-framework/operator-sdk#6187

But understand if there is a more pressing need to bump this.

@tkrishtop

[tkrishtop]

Would love to wait for this to land: operator-framework/operator-sdk#6187

But understand if there is a more pressing need to bump this.

@tkrishtop

Oh, 4.12 security labels, I had to add them as well to run the preflight check on 4.12, it's nice to know that the proper solution is coming.

@bcrochet thanks for checking the PR! I'm not sure how long we'll have to wait for #6187 to be merged. The discussion has been ongoing for 2 months already. I'd prefer to merge 1.26.0 and move forward with these annoying scorecard timeouts - they happen all the time when you run 20 preflight check operator in one job. I tested my change on the latest GA for 4.11, and everything looks safe.

[bcrochet]

Would love to wait for this to land: operator-framework/operator-sdk#6187
But understand if there is a more pressing need to bump this.
@tkrishtop

Oh, 4.12 security labels, I had to add them as well to run the preflight check on 4.12, it's nice to know that the proper solution is coming.

@bcrochet thanks for checking the PR! I'm not sure how long we'll have to wait for #6187 to be merged. The discussion has been ongoing for 2 months already. I'd prefer to merge 1.26.0 and move forward with these annoying scorecard timeouts - they happen all the time when you run 20 preflight check operator in one job. I tested my change on the latest GA for 4.11, and everything looks safe.

Fair enough.

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: acornett21, bcrochet, tkrishtop

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [acornett21,bcrochet]

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