A bugzilla issue was raised [1] concerning the Kiali Operator not defining a skipRange which makes it more difficult to upgrade in a disconnected environment.

The issue [2] was fixed upstream [3].

We need to ensure this is fixed in our upcoming OSSM 2.2 production release of the Kiali operator.

It should be fixed without doing anything assuming our OSSM 2.2 Kiali operator is based on today's master branch's default ansible role (and that should be the case - we will copy the default ansible role from the master branch, call it the v1.47 role (or whatever the version will be), and use that in our production build). But this Jira is here to track this just to make sure we ensure the skipRange is defined in the OSSM 2.2 Kiali operator.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2047566

[2] https://github.com/kiali/kiali/issues/4715

[3] https://github.com/kiali/kiali-operator/pull/492