Revert "Release FortiADCIngressController: 2.0.1"

This reverts commit 710fe47.

README.md

@@ -33,7 +33,7 @@ FortiADC, as the Ingress-managed load balancer, not only provides flexibility in
     <thead>
         <tr>
             <th>Product</th>
-            <th colspan=5>Version</th>   
+            <th colspan=4>Version</th>   
         </tr>
     </thead>
     <tbody>
@@ -43,33 +43,27 @@ FortiADC, as the Ingress-managed load balancer, not only provides flexibility in
             <td>1.0.1</td>
             <td>1.0.2</td>
             <td>2.0.0</td>
-            <td>2.0.1</td>
         </tr>
         <tr>
             <td>Kubernetes</td>
             <td>1.19.8-1.23.x</td>
             <td>1.19.8-1.24.x</td>
             <td colspan=2>1.19.8-1.27.x</td>
-            <td>1.19.8-1.28.x</td>
         </tr>
         <tr>
             <td>FortiADC</td>
-            <td colspan=5>5.4.5 - 7.4.x*</td>
+            <td colspan=4>5.4.5 - 7.4.x*</td>
         </tr>
 	    <tr>
             <td>Openshift Container platform</td>
             <td colspan=3>Not supported</td>
-            <td colspan=2> 4.7-4.12.x</td>
+            <td> 4.7-4.12.x</td>
         </tr>
     </tbody>
 </table>
 
->[!NOTE]
+>**Note** 
 >Some features for FortiADC Ingress Controller version >= 2.0.0 require FortiADC version >= 7.4.0 to support. Please check the [release notes](https://github.com/fortinet/fortiadc-ingress/blob/main/Release-Notes.md).
-
->[!WARNING]
->When using FortiADC Ingress Controller 2.0.x, the Ingress related objects on FortiADC (including virtual servers, content routing, real server pools, and real servers) will be fully managed by the Ingress Controller. This means that any virtual server, content routing, real server pool or real server object that is not deployed by FortiADC Ingress Controller will be removed automatically.
-
 ## Supported Environment
 The FortiADC Ingress Controller has been verified to run in the Openshift Cluster in Openshift Container Platform environment and Kubernetes cluster in the below environments:
 | Environment | Tools for Building |

Release-Notes.md

@@ -1,20 +1,12 @@
 # FortiADC Ingress Controller Release Notes
 
-## 2.0.1
-### What's New
-Support Kubernetes version to 1.28
-### Resolved Issues
- 1. Fix [issue](https://github.com/fortinet/fortiadc-ingress/issues/10) to allow valid hostname and url.
-
 ## 2.0.0
 ### What's New
 
  1. Support Openshift Container Platform 4 with Kubernetes Ingress and OpenShift Route.
  2. Support ingress to expose service with ClusterIP type. This feature requires FortiADC version >= 7.4.0 to support. FortiADC 7.4.0 and FortiADC Ingress Controller 2.0.0 support Flannel with VXLAN backend as the Kubernetes network model CNI plugin. Via the VXLAN tunnel, FortiADC can forward HTTP/HTTPS requests to the Kubernetes service with ClusterIP type.
  3. Support Virtual server FortiGSLB configuration defined in annotation of Kubernetes Ingress.
  4. Add toleration in FortiADC Ingress Controller Helm deployment template. User can customize the toleration time to wait for FortiADC ingress controller spinning up if the Kubernetes node it locates becomes unreachable or goes into NotReady state. The default toleration time for in FortiADC Ingress Controller is 30 seconds. You can check Kubernetes [taints and tolerations](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) for more details.
- 5. Support declarative api for full synchronization. Be aware of using FortiADC version < 7.4, only 
- global administrator has the persmssion to call declarative api.
 ### Resolved Issues
  1. Fix [issue](https://github.com/fortinet/fortiadc-ingress/issues/7) to allow non-global administrator to operate the Ingress
 
@@ -31,4 +23,3 @@ Support Kubernetes version to 1.24
 
  FortiADC Ingress Controller combines the capabilities of an Kubernetes Ingress resource with the Ingress-managed loadbalancer, FortiADC. FortiADC, as the Ingress-managed load-balancer, not only provides flexibility in load-balancing, but also guarantees more security with features such as the Web Application Firewall (WAF), Antivirus Scanning, and Denial of Service (DoS) prevention to protect the web server resources in the Kubernetes cluster. 
  Other features such as health check, traffic log management, and FortiView on FortiADC facilitates the management of the Kubernetes ingress resources.
-