Docs: add upgrade from v2.0/2.1 to v2.2 with API changes

- add example of default instance config
- update channel image
- add new images for api changes
- add limitation resource cleanup when switch namespace

Signed-off-by: Wen Zhou <[email protected]>

src/content/docs/quick-installation-new-operator.md

@@ -22,7 +22,60 @@ For the purposes of this quick start, we used [try.openshift.com](https://try.op
 
 Tutorials will require an OpenShift cluster with a minimum of 16 CPUS and 32GB of memory across all OpenShift worker nodes.
 
-### Installing the New Open Data Hub Operator
+### Upgrade from v2.0/v2.1 to v2.2 and forth release
+
+#### Cleanup resource in cluster
+
+To upgrade, follow these steps:
+
+- Disable the component(s) in your DataScienceCluster instance.
+- Delete both the DataScienceCluster instance and DSCInitialization instance.
+- Click "uninstall" Open Data Hub operator.
+- Delete 2 CRD
+  - Click `Administration` then `CustomResourceDefinitions`, search for `DSCInitialization`
+  - Under `Latest version` column, if shows `v1alpha1`, click "Edit" button(3 dots) on the right, and `Delete CustomResourceDefinition`
+  - Repeat the same procedure on `DataScienceCluster`
+
+All of the above steps can be performed either through the console UI or via the `oc`/`kubectl` CLI.
+After completing these steps, please refer to the installation guide to proceed with a clean installation of the v2.2+ operator.
+
+#### API change
+
+- when create or update DataScienceCluster instance, API version has been upgraded from `v1alpha1` to `v1`
+  - schema in `v1alpha1` API
+      to enabled each component: `.spec.components.[component_name].enabled: true`
+      to disable each component: `.spec.components.[component_name].enabled: false`
+
+  - schema in `v1` API
+      to enabled each component: `.spec.components.[component_name].managementState: Managed`
+      to disable each component: `.spec.components.[component_name].managementState: Removed`
+
+   Example for default DataScienceCluster instance in v2.2
+
+   ```shell
+   apiVersion: datasciencecluster.opendatahub.io/v1
+   kind: DataScienceCluster
+   metadata:
+      name: default
+   spec:
+      components:
+         codeflare:
+            managementState: Removed
+         dashboard:
+            managementState: Managed
+         datasciencepipelines:
+            managementState: Managed
+         kserve:
+            managementState: Removed
+         modelmeshserving:
+            managementState: Managed
+         ray:
+            managementState: Removed
+         workbenches:
+            managementState: Managed
+   ```
+
+### Installing v2.X Open Data Hub Operator
 
 The Open Data Hub operator is available for deployment in the OpenShift OperatorHub as a Community Operators. You can install it from the OpenShift web console by following the steps below:
 
@@ -47,6 +100,8 @@ The Open Data Hub operator is available for deployment in the OpenShift Operator
 
 1. Click on the `Open Data Hub Operator` from `Installed Operators` page to bring up the details for the version that is currently installed.
    ![Open Data Hub Operator](../assets/img/pages/docs/quick-installation-new-operator/odh-operator.png "Open Data Hub Operator")
+   start from v2.2 release, we do not include odh-dashboard CRD in operator, you should see this instead:
+   ![Open Data Hub Operator2.2](../assets/img/pages/docs/quick-installation-new-operator/odh-operator2.png "Open Data Hub Operator2.2")
 
 2. Two ways to create DataScienceCluster instance:
    - Click `Create DataScienceCluster` button from the top warning dialog `DataScienceCluster required(Create a DataScienceCluster instance to use this Operator.)`
@@ -59,10 +114,14 @@ The Open Data Hub operator is available for deployment in the OpenShift Operator
       1. fill in `Name` field
       2. in the `components` section, by clicking `>` it expands currently supported core components. Check the set of components enabled by default and tick/untick the box in each component section to tailor the selection.
       ![Create DSC2](../assets/img/pages/docs/quick-installation-new-operator/create-dsc-component1.png "Create DSC2")
+      start from v2.2.0 refer to below screenshot instead:
+      ![Create DSC2 v2.3](../assets/img/pages/docs/quick-installation-new-operator/create-dsc-component3.png "Create DSC2 v2.3")
 
    - Configure via "YAML view":
       1. write config in YAML format
       2. get detail schema by expanding righthand sidebar ![Create DSC1](../assets/img/pages/docs/quick-installation-new-operator/create-dsc-component2.png "Create DSC1")
+      start from v2.2.0 refer to below screenshot instead:
+      ![Create DSC1 v2.3](../assets/img/pages/docs/quick-installation-new-operator/create-dsc-component4.png "Create DSC1 v2.3")
       3. read [ODH Core components](../tiered-components) to get the full list of supported components
 
 4. Click `Create` button to finalize creation process in seconds.
@@ -86,3 +145,12 @@ The Open Data Hub operator is available for deployment in the OpenShift Operator
 
 - to use "modelmesh" component, users are required to install one operator via OperatorHub before enable it in DataScienceCluster CR
    1. Prometheus Operator from "Community" catalog.
+
+### Limitation
+
+We offer a feature that allows users to configure the namespace for their application. By default, the ODH operator utilizes the `opendatahub` namespace. However, users have the flexibility to opt for a different namespace of their choice. This can be accomplished by modifying the `DSCInitialization` instance with the `.spec.applicationsNamespace` field.
+
+There are two scenarios in which this feature can be utilized:
+
+- Assigning a New Namespace: Users can set a new namespace using `DSCInitialization` instance before creating the `DataScienceCluster` instance.
+- Switching to a New Namespace: Users have the option to switch to a new namespace after resources have already been established in the application's current namespace. It's important to note that in this scenario, only specific resources (such as deployments, configmaps, networkpolicies, roles, rolebindings, secrets etc) will be removed from the old application namespace during cleanup. For namespace-scoped CRD instances, users will be responsible to cleanup themselves.