[DOC] Upgrade for 0.12

[PaulRMellor]

Type of change

• Documentation

Description

Updates to the Upgrade chapter
Following consultation, the x to y Cluster Operator upgrade procedures have been replaced with a generic cluster operator upgrade procedure. The generic procedure now includes a link to the resource updates chapter in the final step.

Additionally, the attributes used in the Kafka upgrade procedures -- lower and higher Kafka version and log version -- have been updated to 2.1.1 and 2.2.0 and 2.1 and 2.2 respectively.

Checklist

Please go through this checklist and make sure all applicable tasks have been done

• Update/write design documentation in ./design
• Write tests
• Make sure all tests pass
• Update documentation
• Check RBAC rights for Kubernetes / OpenShift roles
• Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
• Reference relevant issue(s) and close them after merging
• Update CHANGELOG.md

[tombentley]

LGTM

[d-laing]

Looks good to me. Just one comment.

[PaulRMellor]

@scholzj - are we ready to merge?

[scholzj]

No, I haven't reviewed it yet.

[scholzj]

(I will do it this afternoon)

…

On Fri, May 31, 2019, 11:31 PaulRMellor ***@***.***> wrote: @scholzj <https://github.com/scholzj> - are we ready to merge? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1659?email_source=notifications&email_token=ABLFOR47PKSDSZFLVOVX4PLPYDV5TA5CNFSM4HQLRPEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWUXCUI#issuecomment-497643857>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABLFOR5N4WV3N4AEH3ESNGTPYDV5TANCNFSM4HQLRPEA> .

[scholzj]

Looks quite good. My main concern is that this does not make it clear that it talks about the upgrade from 0.11.x to 0.12.x. We should make it more clear that for any older version upgrades the users should look up the older docs.