Add a note about olm.maxOpenShiftVersion annotation

Author: xenolinux

modules/osdk-control-compat.adoc

@@ -45,6 +45,12 @@ Operators that use deprecated APIs can adversely impact critical workloads when
 
 . If you know that a specific bundle of your Operator is not supported and will not work correctly on {product-title} later than a certain cluster version, configure the maximum version of {product-title} that your Operator is compatible with. In your Operator project's cluster service version (CSV), set the `olm.maxOpenShiftVersion` annotation to prevent administrators from upgrading their cluster before upgrading the installed Operator to a compatible version:
 +
+[IMPORTANT]
+====
+You must use `olm.maxOpenShiftVersion` annotation only if your Operator bundle version cannot work in later versions. Be aware that cluster admins cannot upgrade their clusters with your solution installed. If you do not provide later version and a valid upgrade path,
+cluster admins may uninstall your Operator and can upgrade the cluster version.
+====
+
 .Example CSV with `olm.maxOpenShiftVersion` annotation
 [source,yaml]
 ----