Add OSDK v1.8.0 upgrade guide for OCP 4.8

[adellape]

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

OCP 4.8 supports OSDK v1.8.0, and this new guide shows how to manually upgrade your existing Operator projects for compatibility with the new OSDK version.

Preview: Upgrading projects for newer Operator SDK versions

[netlify]

✔️ Deploy Preview for osdocs ready!

🔨 Explore the source changes: d7b1e95

🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/60dbe633525732000817cda3

😎 Browse the preview: https://deploy-preview-33613--osdocs.netlify.app

[mikemckiernan]

YAML with a blank line? As long as you feel like customers can recognize what to specify for the resourceName field, then it's cool by me. I don't know the subject area, so I'm unsure.

[adellape]

Hm yeah I'm not sure either. Came from https://github.com/operator-framework/operator-sdk/blob/2a1bd03/testdata/ansible/memcached-operator/config/manager/controller_manager_config.yaml.

I'll change the value to a user-replaceable <resource_name> for now. @rashmigottipati @varshab1210 Do you have a suggestion?

[mikemckiernan]

Please check for the oops, otherwise, you know what to act on and what to ignore better than I do.

Interesting read.

[cuipinghuo]

@adellape I only have one suggestion for this pr.
for Upgrading projects for newer Operator SDK versions

`7.Make the following changes to your config/rbac/leader_election_role.yaml file:

a. For Ansible- and Helm-based Operator projects, add role rules for leader election.

Add the rule for the apiGroups, coordination.k8s.io, and resource leases in the config/rbac/leader_election_role.yaml file:

Expand all

config/rbac/leader_election_role.yaml file`

I think it should be

- apiGroups:
  - coordination.k8s.io
  resources:
  - leases
  verbs:
  - get
  - list
  - watch
  - create
  - update
  - patch
  - delete

and no need to change b.Move leases.coordination.k8s.io to its own proxy-role rule.
Although the current version(looking a.+b. as a whole) is the same with what I suggest, it is really confusing. Because in a. you add coordination.k8s.io, but in b. you delete it and add back again.

[adellape]

Although the current version(looking a.+b. as a whole) is the same with what I suggest, it is really confusing. Because in a. you add coordination.k8s.io, but in b. you delete it and add back again.

@cuipinghuo You're right! I've combined the changes for step 7 (no more 7a and 7b).

[adellape]

/cherrypick enterprise-4.8

[openshift-cherrypick-robot]

@adellape: new pull request created: #34155

Details

In response to this:

/cherrypick enterprise-4.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/test-infra repository.