Rel notes known bugs update (#238)

* Updated OSX CLI version from 0.3.0 to 1.0.0.

* OSX CLI version update

* Updated Pack URLs.

* Updated Pack URLs again.

* Removed repetition in custom registry prerequisites.

* Getting started internal URLs repaired.

* Added GCP sections

* Removed 'Your First ABC Cluster' from the ToC by converting them to h2 tags.

* Removed 'Your First ABC Cluster' from the ToC by converting them to h2 tags.

* Edits to creating the first VMware cluster.

* Updates to CLI PUSH flags. Edits to remove dot slash.

* Replaced a placeholder with a link.

* Release notes 1.1

* Updated a link to CLI Push Flags in Rel 1.1 notes.

* Updated all occurrences of 1.0.0 to 1.1.0

* Grammarly edits.

* Added points of interest to dashboard screenshots.

* Rectified the code of points of interest for dashboard screenshots.

* vmware pre-requisites added

* changed internt typo

* Added tooltips

* CLI and Regs and Packs version update

* Sample API workflow (template only), minor typos in api.json

* removed 3 addl layers in sample api workflow

* removed 3 addl layers in sample api workflow from the text

* Added an info box into custom registry page related to the DOC-59 bug.

* Added the proxy whitelist table.

* rel notes 1.2

* Changes bring the 'HTTP Mode' section out of the info box under 'deploying pack reg server'.

* Changes mentioned in DOC-63 - updated VMware arch image and NO PROXY.

* On prem docs first draft.

* First Draft of Super Admin Dashboard

* Added on-prem and SaaS tabs to the VMware tab in Getting Started. Info boxes in VMware tab in Clusters.

* Adding info as per doc-48

* Changes from DOC-65

* Typo correction.

* Homepage Changes

* minor edits to the system console dashboard page

* Updating links in the on-prem docs.

* CLI URLs updated to reflect v1.5

* Adding BET-1491, BET-1472 and BET-1461 to Known Issues.

Author: abhikb2005

packages/docs/content/13-release-notes.md

@@ -61,8 +61,15 @@ The following features are included as part of Spectro Cloud 1.0:
 * Grouping of clusters logically into Projects for governance and control.
 * Rich set of enterprise features such as granular RBAC, Single Sign-on, detailed Audit logs, etc.
 
-## Known Issues
-
+# Known Issues
+
+* **BET-1491:** Portworx currently does not [support](https://docs.portworx.com/portworx-install-with-kubernetes/) Kubernetes version 1.19. This results in a failure to bring up the Stork scheduler pod.
+* **BET-1472:** In the [Enterprise Mode](/enterprise-version/deploying-an-enterprise-cluster/#enterprisemode), deleting a node in an Enterprise cluster renders the cluster unusable due to an [in-tree limitation](https://github.com/vmware/vsphere-storage-for-kubernetes/issues/55).
+    * *Recommendations:*
+        * To prevent VMDK deletion with the in-tree provider, drain the node, let all pods re-schedule on another node, let all volumes detach from the node, and then finally delete the node VM.
+        * This issue is resolved with [vSphere 67u3](https://docs.vmware.com/en/VMware-vSphere/6.7/Cloud-Native-Storage/GUID-51D308C7-ECFE-4C04-AD56-64B6E00A6548.html) and a [new CSI driver](https://github.com/kubernetes-sigs/vsphere-csi-driver).
+        * A [related issue](https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/359) might occur where a persistent volume might not attach to a new node.
+* **BET-1461:** For AWS clusters, when the Static VPC option is used, clusters might not complete provisioning. This bug will be patched in subsequent releases.
 * **BET-768:** On the Azure cloud, the choice of Availability Zones (AZ) may be ignored if the selected AZs do not support the requested VM size. Non-Zoned VMs are created in such cases without a warning to the user.
 
 <InfoBox>