LOG-5587: fix provider so operator is evaluated as official

[jcantrill]

Description

This PR:

• updates the provider in the manifest so the console will evaluate it as an official Red Hat operator

Links

https://issues.redhat.com/browse/LOG-5587

[openshift-ci-robot]

@jcantrill: This pull request references LOG-5587 which is a valid jira issue.

In response to this:

Description

This PR:

• updates the provider in the manifest so the console will evaluate it as an official Red Hat operator

Links

https://issues.redhat.com/browse/LOG-5587

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.

[jcantrill]

/cherrypick master

[openshift-cherrypick-robot]

@jcantrill: once the present PR merges, I will cherry-pick it on top of master in a new PR and assign it to you.

In response to this:

/cherrypick master

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.

[jcantrill]

/cherrypick release-5.8

[openshift-cherrypick-robot]

@jcantrill: once the present PR merges, I will cherry-pick it on top of release-5.8 in a new PR and assign it to you.

In response to this:

/cherrypick release-5.8

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill

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 [jcantrill]

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

[openshift-ci]

@jcantrill: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[Clee2691]

/lgtm

[openshift-cherrypick-robot]

@jcantrill: #2828 failed to apply on top of branch "release-5.8":

Applying: NO-JIRA: Update golang builder and dev tools for 1.22
Using index info to reconstruct a base tree...
A	bundle/manifests/cluster-logging.clusterserviceversion.yaml
A	config/manifests/bases/cluster-logging.clusterserviceversion.yaml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): config/manifests/bases/cluster-logging.clusterserviceversion.yaml deleted in HEAD and modified in NO-JIRA: Update golang builder and dev tools for 1.22. Version NO-JIRA: Update golang builder and dev tools for 1.22 of config/manifests/bases/cluster-logging.clusterserviceversion.yaml left in tree.
CONFLICT (modify/delete): bundle/manifests/cluster-logging.clusterserviceversion.yaml deleted in HEAD and modified in NO-JIRA: Update golang builder and dev tools for 1.22. Version NO-JIRA: Update golang builder and dev tools for 1.22 of bundle/manifests/cluster-logging.clusterserviceversion.yaml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 NO-JIRA: Update golang builder and dev tools for 1.22

In response to this:

/cherrypick release-5.8

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-cherrypick-robot]

@jcantrill: #2828 failed to apply on top of branch "master":

Applying: NO-JIRA: Update golang builder and dev tools for 1.22
Using index info to reconstruct a base tree...
M	bundle/manifests/cluster-logging.clusterserviceversion.yaml
M	config/manifests/bases/cluster-logging.clusterserviceversion.yaml
Falling back to patching base and 3-way merge...
Auto-merging config/manifests/bases/cluster-logging.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in config/manifests/bases/cluster-logging.clusterserviceversion.yaml
Auto-merging bundle/manifests/cluster-logging.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in bundle/manifests/cluster-logging.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 NO-JIRA: Update golang builder and dev tools for 1.22

In response to this:

/cherrypick master

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.