Reorganize hosted and self-hosted cloud pages. Add Cosmic cloud to list of clouds (#285)

* Reorganize hosted and self-hosted cloud pages. Add Cosmic Cloud to the list of available clouds

Signed-off-by: Dom Del Nano <ddelnano@gmail.com>

* Fix grammar

Signed-off-by: Dom Del Nano <ddelnano@gmail.com>

Author: ddelnano

content/en/01-about-pixie/05-faq.md

@@ -60,13 +60,13 @@ Yes. See the self-hosted [Install Guide](/installing-pixie/install-guides/self-h
 
 ### Does Pixie offer a hosted cloud offering?
 
-Yes. Pixie Community Cloud is a hosted version of Pixie. Pixie stores all data on the customer's cluster, resulting in a very small cloud footprint which allows Pixie to offer the Community Cloud offering 100% free for all Pixie users. See the Community Cloud [Install Guide](/installing-pixie/install-guides/community-cloud-for-pixie) to get started.
+Yes, there are a few versions of hosted Pixie. Please see the [Hosted Pixie](/installing-pixie/install-guides/hosted-pixie) page for all the current offerings.
 
 ## Data Collection
 
 ### Where does Pixie store its data?
 
-Pixie stores the data it collects in-memory on the nodes in your cluster; no data is sent to a centralized backend outside of the cluster. This is true for both self-hosted Pixie and [Pixie Community Cloud](#general-does-pixie-offer-a-hosted-cloud-offering).
+Pixie stores the data it collects in-memory on the nodes in your cluster; no data is sent to a centralized backend outside of the cluster. This is true for both [hosted](#general-does-pixie-offer-a-hosted-cloud-offering) and self-hosted Pixie.
 
 Pixie has a [1GiB memory requirement](/installing-pixie/requirements/#memory) per node. After installing Pixie, it is normal to see a temporary increase in memory usage of the `vizier-pem` pods as they begin to fill their [data tables](/reference/datatables/).
 
@@ -80,7 +80,7 @@ Pixie's [Plugin System](/reference/plugins/plugin-system) integrates with third-
 
 Pixie stores the telemetry data it collects in-memory on the nodes in your cluster. Data processing and script execution are also performed in the cluster. End-to-end encryption is offered for data in flight between in-cluster storage and presentation in the UI, CLI, and API.
 
-Pixie Cloud (self-hosted or Pixie Community Cloud) hosts the UI and stores limited metadata related to account (user, organization) and Kubernetes control data (cluster name, number of nodes, etc). All communication with Pixie Cloud is TLS encrypted.
+Pixie Cloud (hosted or self-hosted Pixie) hosts the UI and stores limited metadata related to account (user, organization) and Kubernetes control data (cluster name, number of nodes, etc). All communication with Pixie Cloud is TLS encrypted.
 
 Data flows through Pixie's Cloud via a reverse proxy as encrypted traffic without any persistence. This allows developers to access data without being in the same network as the cluster.
 

content/en/02-installing-pixie/03-install-guides/01-hosted-pixie/01-cosmic-cloud.md

@@ -0,0 +1,156 @@
+---
+title: "Cosmic Cloud"
+metaTitle: "Install | Install Guides | Cosmic Cloud"
+metaDescription: "Getting started guide to setup Pixie"
+order: 1
+---
+
+## Prerequisites
+
+- Review Pixie's [requirements](/installing-pixie/requirements) to make sure that your Kubernetes cluster is supported.
+
+- Determine if you already have [Operator Lifecycle Manager](https://docs.openshift.com/container-platform/4.5/operators/understanding/olm/olm-understanding-olm.html) (OLM) deployed to your cluster, possibly to the default `olm` namespace. Pixie uses the Kubernetes [Operator pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) to manage its Vizier, which handles data collection and query execution (see the [Architecture](/about-pixie/what-is-pixie/#architecture) diagram). The OLM is used to install, update and manage the Vizier Operator.
+
+- Pixie interacts with the Linux kernel to install BPF programs to collect telemetry data. In order to install BPF programs, Pixie [`vizier-pem-*`](/about-pixie/what-is-pixie/#architecture) pods require [privileged access](https://github.com/pixie-io/pixie/blob/e03434a5e41d82159aa7602638804159830f9949/k8s/vizier/base/pem_daemonset.yaml#L115).
+
+## 1. Sign up
+
+Visit our [product page](https://work.getcosmic.ai/) and sign up.
+
+## 2. Set up a Kubernetes cluster (optional)
+
+If you don't have a Kubernetes cluster available, you can set up Minikube as a local sandbox environment following these [instructions](/installing-pixie/setting-up-k8s/minikube-setup).
+
+## 3. Install the Pixie CLI
+
+The easiest way to install Pixie's CLI is using the install script:
+
+```bash
+# Copy and run command to install the Pixie CLI.
+bash -c "$(curl -fsSL https://getcosmic.ai/install.sh)"
+```
+
+For alternate install options (Docker, Debian package, RPM, direct download of the binary) see the [CLI Install](/installing-pixie/install-schemes/cli/) page.
+
+## 4. Deploy Pixie 🚀
+
+Pixie's CLI is the fastest and easiest way to deploy Pixie. You can also deploy Pixie using [YAML](/installing-pixie/install-schemes/yaml) or [Helm](/installing-pixie/install-schemes/helm). You can use these steps to install Pixie to one or more clusters.
+
+To deploy Pixie using the CLI:
+
+<Alert variant="outlined" severity="info">
+  If your cluster already has Operator Lifecycle Manager (OLM) deployed, deploy Pixie using the `--deploy_olm=false` flag.
+</Alert>
+
+<Alert variant="outlined" severity="info">
+  Please refer to <a href="/reference/admin/environment-configs">Environment-Specific Configurations</a> for other configurations that should be set for your specific Kubernetes environment.
+</Alert>
+
+```bash
+# PL_CLOUD_ADDR must be set before any pixie cli commands are run!
+export PL_CLOUD_ADDR=getcosmic.ai
+
+# List Pixie deployment options.
+px deploy --help
+
+# Deploy the Pixie Platform in your K8s cluster (No OLM present on cluster).
+px deploy
+
+# Deploy the Pixie Platform in your K8s cluster (OLM already exists on cluster).
+px deploy --deploy_olm=false
+
+# Deploy Pixie with a specific memory limit (2Gi is the default, 1Gi is the minimum recommended)
+px deploy --pem_memory_limit=1Gi
+```
+
+Pixie deploys the following pods to your cluster. Note that the number of `vizier-pem` pods correlates with the number of nodes in your cluster, so your  deployment may contain more PEM pods.
+
+```bash
+NAMESPACE           NAME
+olm                 catalog-operator
+olm                 olm-operator
+pl                  kelvin
+pl                  nats-operator
+pl                  pl-nats-1
+pl                  vizier-certmgr
+pl                  vizier-cloud-connector
+pl                  vizier-metadata
+pl                  vizier-pem
+pl                  vizier-pem
+pl                  vizier-proxy
+pl                  vizier-query-broker
+px-operator         77003c9dbf251055f0bb3e36308fe05d818164208a466a15d27acfddeejt7tq
+px-operator         pixie-operator-index
+px-operator         vizier-operator
+```
+
+To deploy Pixie to another cluster, change your `kubectl config current-context` to point to that cluster. Then repeat the same deploy commands shown in this step.
+
+### More Deploy Options
+
+For more deploy options that you can specify to configure Pixie, refer to our [deploy options](/reference/admin/deploy-options).
+
+## 5. Invite others to your organization (optional)
+
+Add users to your organization to share access to Pixie Live Views, query running clusters, and deploy new Pixie clusters. For instructions, see the [User Management & Sharing](/reference/admin/user-mgmt) reference docs.
+
+## 6. Use Pixie
+
+### Deploy a demo microservices app (optional)
+
+Deploy a simple demo app to monitor using Pixie:
+
+```bash
+# List available demo apps.
+px demo list
+
+# Example: deploy Weaveworks' "sock-shop".
+px demo deploy px-sock-shop
+```
+
+This demo application takes several minutes to stabilize after deployment.
+
+To check the status of the application's pods, run:
+
+```bash
+kubectl get pods -n px-sock-shop
+```
+
+### Test out the CLI
+
+Use `px live` to run a script to demonstrate observability. The `http_data` script shows a sample of the HTTP/2 traffic flowing through your cluster.
+
+```bash
+# List built-in scripts
+px scripts list
+
+# Run a script
+px live px/http_data
+```
+
+For more information, checkout our [CLI guide](/using-pixie/using-cli/).
+
+### Explore the web app
+
+Open [Pixie's Live UI](https://work.getcosmic.ai) in a new tab.
+
+1. After reviewing the hints, click the X in the upper left hand corner of the screen.
+2. Select your cluster (you may see other clusters from members of your organization).
+3. Now, select a script, e.g. `px/cluster` or `px/http_data`.
+
+For more information, check out our [Live UI guide](/using-pixie/using-live-ui/).
+
+### Check out the tutorials
+
+Learn how to use Pixie for
+
+- [Network Monitoring](/tutorials/pixie-101/network-monitoring/)
+- [Infra Health](/tutorials/pixie-101/infra-health/)
+- [Service Performance](/tutorials/pixie-101/service-performance/)
+- [Database Query Profiling](/tutorials/pixie-101/database-query-profiling/)
+- [Request Tracing](/tutorials/pixie-101/request-tracing/)
+- [Kafka Monitoring](/tutorials/pixie-101/kafka-monitoring/)
+
+## Get Help
+
+Please see our [Troubleshooting](/about-pixie/troubleshooting/) guide, reach out on our [Community Slack](https://slackin.px.dev/) or file an issue on [GitHub](https://github.com/pixie-io/pixie/issues).

…l-guides/01-community-cloud-for-pixie.md …es/01-hosted-pixie/02-new-relic-cloud.mdcontent/en/02-installing-pixie/03-install-guides/01-community-cloud-for-pixie.md renamed to content/en/02-installing-pixie/03-install-guides/01-hosted-pixie/02-new-relic-cloud.md content/en/02-installing-pixie/03-install-guides/01-community-cloud-for-pixie.md renamed to content/en/02-installing-pixie/03-install-guides/01-hosted-pixie/02-new-relic-cloud.md

@@ -1,8 +1,8 @@
 ---
-title: "New Relic - Community Cloud"
-metaTitle: "Install | Install Guides | New Relic - Community Cloud"
+title: "New Relic Cloud"
+metaTitle: "Install | Install Guides | New Relic Cloud"
 metaDescription: "Getting started guide to setup Pixie"
-order: 1
+order: 2
 ---
 
 ## Prerequisites

content/en/02-installing-pixie/03-install-guides/01-hosted-pixie/index.md

@@ -0,0 +1,19 @@
+---
+title: "Hosted Pixie"
+metaTitle: "Hosted Pixie"
+metaDescription: "Install instructions for the various Hosted Pixie offerings"
+order: 1
+redirect_from:
+    - /installing-pixie/install-guides/community-cloud-for-pixie
+---
+
+This page lists all of the current hosted Pixie offerings. Use the links below to navigate to the install instructions for your preferred Cloud:
+- [Cosmic Cloud](/installing-pixie/install-guides/hosted-pixie/cosmic-cloud)
+- [New Relic Cloud](/installing-pixie/install-guides/hosted-pixie/new-relic-cloud)
+
+When browsing this site, use the "Cloud backend" dropdown to update the links to match your selected Cloud.
+
+
+## Add Your Own
+
+Does your organization offer Pixie? [Open a PR](https://github.com/pixie-io/pixie-docs) to list it here.

…xie/03-install-guides/03-airgap-pixie.md …/02-self-hosted-pixie/01-airgap-pixie.mdcontent/en/02-installing-pixie/03-install-guides/03-airgap-pixie.md renamed to content/en/02-installing-pixie/03-install-guides/02-self-hosted-pixie/01-airgap-pixie.md content/en/02-installing-pixie/03-install-guides/03-airgap-pixie.md renamed to content/en/02-installing-pixie/03-install-guides/02-self-hosted-pixie/01-airgap-pixie.md

@@ -5,6 +5,7 @@ metaDescription: "How to install Pixie in an air gapped environment."
 order: 3
 redirect_from:
     - /airgap
+    - /installing-pixie/install-guides/airgap-pixie
 ---
 
 Follow these instructions to install Pixie in an air gapped environment. An air gapped environment is any environment that is not directly connected to the Internet.

…nstall-guides/04-production-readiness.md …-hosted-pixie/02-production-readiness.mdcontent/en/02-installing-pixie/03-install-guides/04-production-readiness.md renamed to content/en/02-installing-pixie/03-install-guides/02-self-hosted-pixie/02-production-readiness.md content/en/02-installing-pixie/03-install-guides/04-production-readiness.md renamed to content/en/02-installing-pixie/03-install-guides/02-self-hosted-pixie/02-production-readiness.md

@@ -3,6 +3,8 @@ title: "Production Readiness"
 metaTitle: "Production Readiness"
 metaDescription: "Sharing a single Pixie Cloud across multiple Pixie deployments"
 order: 4
+redirect_from:
+    - /installing-pixie/install-guides/production-readiness
 ---
 
 Pixie allows you to connect multiple Kubernetes clusters to a single Pixie Cloud instance. The main advantage of such a deployment is that you can monitor all your Kubernetes clusters from a single point. 

…3-install-guides/02-self-hosted-pixie.md …all-guides/02-self-hosted-pixie/index.mdcontent/en/02-installing-pixie/03-install-guides/02-self-hosted-pixie.md renamed to content/en/02-installing-pixie/03-install-guides/02-self-hosted-pixie/index.md content/en/02-installing-pixie/03-install-guides/02-self-hosted-pixie.md renamed to content/en/02-installing-pixie/03-install-guides/02-self-hosted-pixie/index.md

@@ -5,7 +5,7 @@ metaDescription: "Getting started guide to setup 100% self-hosted Pixie"
 order: 2
 ---
 
-Get Pixie fully managed with [Pixie Community Cloud](/installing-pixie/install-guides/community-cloud-for-pixie) (free forever) or run on your own infrastructure with the following self-managed option.
+Get Pixie fully managed with one of the [Hosted Pixie offerings](/installing-pixie/install-guides/hosted-pixie) or run on your own infrastructure with the following self-managed option.
 
 ## Prerequisites
 
@@ -19,10 +19,6 @@ Get Pixie fully managed with [Pixie Community Cloud](/installing-pixie/install-g
 
 ## 1. Deploy Pixie Cloud
 
-<Alert variant="outlined" severity="info">
-  Pixie also offers a free account with Pixie Community Cloud to make getting started even easier and faster. To get Pixie Cloud, check out the community cloud <a href="/installing-pixie/install-guides/community-cloud-for-pixie">Install Guide</a>.
-</Alert>
-
 <Alert variant="outlined" severity="warning">
   There is a known issue with login on self-managed Pixie Cloud on Safari and Firefox. For now, use Chrome.
 </Alert>

content/en/02-installing-pixie/03-install-guides/index.md

@@ -9,28 +9,23 @@ redirect_from:
 
 There are multiple hosting options for Pixie.
 
-- [Community Cloud for Pixie (easiest)](/installing-pixie/install-guides/community-cloud-for-pixie)
+- [Hosted Pixie (easiest)](/installing-pixie/install-guides/hosted-pixie)
 - [Self-Hosted Pixie](/installing-pixie/install-guides/self-hosted-pixie)
-- [Air Gapped Pixie](/installing-pixie/install-guides/airgap-pixie)
 
 Pixie is a hybrid system, with a cloud component (Pixie Cloud) and an in-cluster component for data persistence and storage (Vizier). See [Architecture](/about-pixie/what-is-pixie/#architecture) for more details.
 
 While Vizier will always be deployed directly onto your Kubernetes cluster, there are multiple options for Pixie Cloud.
 
-## Community Cloud for Pixie (easiest)
+## Hosted Pixie (easiest)
 
-Follow the [Community Cloud for Pixie Guide](/installing-pixie/install-guides/community-cloud-for-pixie) if you want to deploy Pixie without needing to host your own version of Pixie Cloud. Community Cloud for Pixie provides community hosting of the cloud component to simplify your Pixie deployment.
+If you want to deploy Pixie without needing to host your own version of Pixie Cloud, select one of the Cloud offerings on the [Hosted Pixie](/installing-pixie/install-guides/hosted-pixie) page and following the install instructions.
 
-With Community Cloud for Pixie, telemetry data is exclusively stored on your Kubernetes cluster (not in Pixie Cloud).
+When using a hosted Pixie backend, telemetry data is exclusively stored on your Kubernetes cluster (not in Pixie Cloud).
 
 ## Self-Hosted Pixie
 
 Pixie also supports for self-hosting of the entire platform, including Pixie Cloud. Follow the [Self-Hosted Pixie Guide](/installing-pixie/install-guides/self-hosted-pixie) for the steps.
 
-## Air Gapped Pixie
-
-Pixie works in air gapped environments. Follow the [Air Gapped Pixie Guide](/installing-pixie/install-guides/airgap-pixie) for the install steps.
-
 ## Add Your Own
 
 Does your organization offer Pixie? [Open a PR](https://github.com/pixie-io/pixie-docs) to list it here.

content/en/02-installing-pixie/04-install-schemes/01-cli.md

@@ -108,12 +108,15 @@ rpm -i pixie-px.x86_64.rpm
 px deploy --help
 
 # Deploy the Pixie Platform in your K8s cluster (No OLM present on cluster).
+export PL_CLOUD_ADDR=<getcosmic.ai or withpixie.ai>
 px deploy
 
 # Deploy the Pixie Platform in your K8s cluster (OLM already exists on cluster).
+export PL_CLOUD_ADDR=<getcosmic.ai or withpixie.ai>
 px deploy --deploy_olm=false
 
 # Deploy Pixie with a specific memory limit (2Gi is the default, 1Gi is the minimum recommended)
+export PL_CLOUD_ADDR=<getcosmic.ai or withpixie.ai>
 px deploy --pem_memory_limit=1Gi
 ```
 

content/en/02-installing-pixie/04-install-schemes/03-helm.md

@@ -55,16 +55,16 @@ helm repo add pixie-operator https://artifacts.px.dev/helm_charts/operator
 helm repo update
 
 # Install the Pixie chart (No OLM present on cluster).
-helm install pixie pixie-operator/pixie-operator-chart --set deployKey=<deploy-key-goes-here> --set clusterName=<cluster-name> --namespace pl --create-namespace
+helm install pixie pixie-operator/pixie-operator-chart --set cloudAddr=<getcosmic.ai:443 or withpixie.ai:443> --set deployKey=<deploy-key-goes-here> --set clusterName=<cluster-name> --namespace pl --create-namespace
 
 # Install the Pixie chart (OLM already exists on cluster).
-helm install pixie pixie-operator/pixie-operator-chart --set deployKey=<deploy-key-goes-here> --set clusterName=<cluster-name> --namespace pl --create-namespace --set deployOLM=false
+helm install pixie pixie-operator/pixie-operator-chart --set cloudAddr=<getcosmic.ai:443 or withpixie.ai:443> --set deployKey=<deploy-key-goes-here> --set clusterName=<cluster-name> --namespace pl --create-namespace --set deployOLM=false
 
 # Install the Pixie chart (Self-hosting Pixie Cloud)
 helm install pixie pixie-operator/pixie-operator-chart --set deployKey=<deploy-key-goes-here> --set clusterName=<cluster-name> --namespace pl --create-namespace --set devCloudNamespace=plc
 
 # Install Pixie with a memory limit for the PEM pods (per node). 2Gi is the default, 1Gi is the minimum recommended.
-helm install pixie pixie-operator/pixie-operator-chart --set deployKey=<deploy-key-goes-here> --set clusterName=<cluster-name> --namespace pl --create-namespace --set deployOLM=false --set pemMemoryLimit=1Gi
+helm install pixie pixie-operator/pixie-operator-chart --set cloudAddr=<getcosmic.ai:443 or withpixie.ai:443> --set deployKey=<deploy-key-goes-here> --set clusterName=<cluster-name> --namespace pl --create-namespace --set deployOLM=false --set pemMemoryLimit=1Gi
 ```
 
 Pixie will deploy pods to the `pl`, `px-operator`, and `olm`(if deploying the OLM) namespaces.