Value Statement

When customer imports a cluster in RHACM they are given the option to copy and run a command. This action is prefaced with the warning"For OpenShift 4 and Kubernetes 1.16.0 clusters or above."  (see attached image) 

This statement may need review as it may cause some confusion. 

It appears the statement is in place and may be referring to CRD's reaching stability in 1.16. 

Based on https://access.redhat.com/solutions/4870701 1.16 was introduced in OCP 4.3

This could mean that OCP 4.1 and 4.2 are incorrectly suggested to be supported with the OCP 4 statement. Whilst these are so old they aren't likely to matter, I'm just suggesting it's time to remove the line just in case.

In addition, RHACM doesn't support any product running K8s at that low a version and the statement might suggest and/or confuse customers.

Proposed Solution

• Could we either remove the statement entirely or ...
• ... replace it with a reference to check the RHACM support matrix at https://access.redhat.com/support/policy/updates/advanced-cluster-management something like "Review version compatibility requirements [here|https://access.redhat.com/support/policy/updates/advanced-cluster-management] before running this command."

Seeing as they likely wouldn't get this far anyway if they have not it may actually be unnecessary anyway (and if so can just be removed).

But if we do create a generic link to that article it will cover future upgrades or issues without needing to be updated "ever" again.

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.