COO-183: Prevent Reconcile Loop for Troubleshooting Panel UIPlugin

[PeterYurkovich]

Although the troubleshooting panel will deploy after #501, it reconciles in a loop.

Since the UIPlugin proxy spec is still of type v1alpha1, when it is created it gets converted to use v1 instead. Having authorize: false creates a v1 version that is different enough from from the v1alpha1 to cause a reconciliation. However, the conversion again happens leading to a loop.

[openshift-ci-robot]

@PeterYurkovich: This pull request references COO-183 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set.

In response to this:

Although the troubleshooting panel with deploy after #501, it reconciles in a loop.

Since the UIPlugin proxy spec is still of type v1alpha1, when it is created it gets converted to use v1 instead. Having authorize: false creates a v1 version that is different enough from from the v1alpha1 to cause a reconciliation. However, the conversion again happens leading to a loop.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @PeterYurkovich. Thanks for your PR.

I'm waiting for a rhobs 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-sigs/prow repository.

[openshift-ci-robot]

@PeterYurkovich: This pull request references COO-183 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.17.0" version, but no target version was set.

In response to this:

Although the troubleshooting panel will deploy after #501, it reconciles in a loop.

Since the UIPlugin proxy spec is still of type v1alpha1, when it is created it gets converted to use v1 instead. Having authorize: false creates a v1 version that is different enough from from the v1alpha1 to cause a reconciliation. However, the conversion again happens leading to a loop.

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 openshift-eng/jira-lifecycle-plugin repository.

[jgbernalp]

/approve
/lgtm

[simonpasquier]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, PeterYurkovich, simonpasquier

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:

• pkg/OWNERS [simonpasquier]

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

[simonpasquier]

/ok-to-test