…rator

Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>

…62-to-release-4.20

[release-4.20] OCPBUGS-61563: [OTE] Update webhook ote tests to use latest webhook-operator

This reverts commit 9cc13d8.

…60-to-release-4.20

[release-4.20] OCPBUGS-61705: Revert "Handle service-ca cert availability/rotation"

…itions (#2169)

When upgrading operators, CRD validation errors can be very large (50KB+).
Kubernetes rejects status updates over 32KB with "Too long: may not be more than 32768 bytes".
This causes ClusterExtension upgrades to fail and get stuck.

Assisted-by: Cursor

…CPBUGS-59518 ) (#2179)

* (fix): unhandle changes for crd upgrade safety

- Keep unhandled spec changes as errors; message: "unhandled changes found"

Assisted-by: Cursor

* enhance to extract details from unhandle issue

…duced in upstream in operator-framework/operator-controller@e88a6ea#diff-0e9c95b80180d8896ba5d48a42bd69332dc3de4b951d391f461ef8f40ff150b0

OCPBUGS-62722: (cherry-pick) Fix truncate large error messages and unhandle changes for crd upgrade safety in status conditions

… deployer SA creation by OCP controller

OCPBUGS-62811: for incompatible test add func to wait builder and deployer SA creation by OCP controller

…77-to-release-4.20

[release-4.20] NO-ISSUE: add jiazha to approvers

* move crd upgrade safety testdata into crdupgradesafety package

Signed-off-by: Joe Lanford <joe.lanford@gmail.com>

* fix: bump crdify to fix bugs and regressions

regression fixes:

1. correctly handle processing of properties that are OpenAPI items
2. allow enums to have values added.

bug fix:

crdify's served version validator was updated to actually compare the
old CRD with the new CRD so that any issues identified in the old CRD
do not continue to be reported when performing comparisons between
served versions of the new CRD.

This effectively allows issues in the served version validations to be
acknowledged once when they are introduced, but then those issues are
essentially grandfathered in such that they do not have to be
acknowledged again in the future.

This issue was actually identified in a case where an operator upgrade
was stopped by the CRD upgrade check despite there being no changes
whatsoever to the CRD. The "old" and "new" CRDs contained the exact
same issues, but since crdify was looking exclusively at the "new" CRD,
it found those issues and reported them.

---------

Signed-off-by: Joe Lanford <joe.lanford@gmail.com>

OCPBUGS-61890: 🐛 CRD upgrade safety fixes and ratcheting (#2123)