Merge pull request #456 from entando/ENDOC-449

ENDOC-449 Remove VMWare Tanzu or note that it’s not actively certified/supported

vuepress/docs/.vuepress/next.js

@@ -220,10 +220,6 @@ module.exports = {
                                 title: 'Google Kubernetes Engine (GKE)',
                                 path: path  + 'getting-started/gke-install.md'
                             },
-                            {
-                                title: 'Tanzu Kubernetes Grid (TKG)',
-                                path: path  + 'getting-started/tanzu-install.md'
-                            },
                             {
                                 title: 'Kubernetes',
                                 path: path + 'getting-started/kubernetes-install.md'

vuepress/docs/next/tutorials/README.md

@@ -59,5 +59,4 @@ table th:nth-of-type(3) {
 | [Set Up Entando on Azure Kubernetes Service (AKS)](./getting-started/azure-install.md) |[Connect Your Entando Application to an External Database](./devops/external-db.md) |
 | [Set Up Entando on Google Kubernetes Engine (GKE)](./getting-started/gke-install.md) | [Install the Standard Demo Application](./solution/install-standard-demo.md)| 
 | [Set Up Entando on Red Hat OpenShift](./getting-started/openshift-install.md) | |
-| [Set Up Entando on Tanzu Kubernetes Grid (TKG)](./getting-started/tanzu-install.md) | |
 

vuepress/docs/next/tutorials/getting-started/kubernetes-install.md

@@ -36,7 +36,7 @@ To install Entando with CMS, the hardware requirements depend on the complexity
 
 ## Backup Strategies
 
-The recommended method to secure your content is to use database services that automate backups and restores on a Kubernetes cluster like Azure, Red Hat OpenShift, Google K8s Service, Tanzu K8s Grid or Amazon Elastic. If this is not an option, there are tools like [Velero](https://velero.io/) and [Cloudcase](https://cloudcasa.io/) to manage them. 
+The recommended method to secure your content is to use database services that automate backups and restores on a Kubernetes cluster like Azure, Red Hat OpenShift, Google K8s Service or Amazon Elastic. If this is not an option, there are tools like [Velero](https://velero.io/) and [Cloudcase](https://cloudcasa.io/) to manage them. 
 
 Note: Some DevOps teams warn against running databases inside pods in production environments.