Add "Upgrading installed Operators"

[adellape]

https://issues.redhat.com/browse/OSDOCS-1261

Preview (internal): http://file.rdu.redhat.com/~adellape/100820/upgrade_operators/operators/admin/olm-upgrading-operators.html

[openshift-docs-preview-bot]

The preview will be available shortly at:

• https://upgrade_operators--ocpdocs.netlify.com/

[codyhoag]

LGTM!

[jianzhangbjz]

/assign @jianzhangbjz

[jianzhangbjz]

That's perfect, looks good to me, thanks! But I didn't find an introduction to the upgrade for the same channel.
I'm not sure if it should be list in this doc. But, anyway, I list it here, actually, this is a feature for the CatalogSource Polling, here is the related test case OCP-27672.
For the upgrade in the same channel, if you subscribe to the operator with Automatic, the installed operator will be upgraded automatically once the Index image updated.
For the Manual way, the installed operator will be upgraded after your approval, like this:

[adellape]

That's perfect, looks good to me, thanks! But I didn't find an introduction to the upgrade for the same channel.

@jianzhangbjz Thank you! I guess I was thinking the couple spots where it's mentioned "If the approval strategy in the Subscription is set to Automatic, the upgrade process initiates immediately" or similar covered that scenario. The title "Manually approving a pending Operator upgrade" is specifically about "manually" approving, and there wouldn't really be a procedure for the automatic scenario.

I'm opening to adding another section more explicitly about that scenario if it's more clear though. I'll move this PR along for now, and can revisit in a follow-up, if needed.

[adellape]

/cherrypick enterprise-4.5

[openshift-cherrypick-robot]

@adellape: #26272 failed to apply on top of branch "enterprise-4.5":

Applying: Add "Upgrading installed Operators"
Using index info to reconstruct a base tree...
M	_topic_map.yml
Falling back to patching base and 3-way merge...
Auto-merging _topic_map.yml
CONFLICT (content): Merge conflict in _topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add "Upgrading installed Operators"
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherrypick enterprise-4.5

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.

[adellape]

/cherrypick enterprise-4.6

[openshift-cherrypick-robot]

@adellape: new pull request created: #26360

Details

In response to this:

/cherrypick enterprise-4.6

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.

[jianzhangbjz]

@adellape Thanks! For this PR, it's only for how to update the operator for different channels. But, actually, if the users want to upgrade the operator in the same channel, they just need to update the Index (CatalogSource) image, and no need to change the Subscription. I guess we should add this point somewhere.