Add syntax highlighting to codeblocks. (#180)

htroisi · web-flow · commit b0fca7c130de · 2022-05-04T22:04:16.000-07:00
Signed-off-by: Hannah Troisi &lt;htroisi@pixielabs.ai&gt;
diff --git a/content/en/01-about-pixie/06-troubleshooting.md b/content/en/01-about-pixie/06-troubleshooting.md
@@ -31,7 +31,7 @@ This page describes how to troubleshoot Pixie. We frequently answer questions on
 
 An initial overview of Pixie can be retrieved by listing all `Vizier` pods to verify whether all pods have the status `Running`:
 
-```shell
+```bash
 $ px debug pods
   NAME                                          PHASE    RESTARTS  MESSAGE  REASON  START TIME
   pl/pl-nats-0                                  RUNNING  0                          2022-04-08T13:17:15-07:00
diff --git a/content/en/02-installing-pixie/02-setting-up-k8s/02-eks-setup.md b/content/en/02-installing-pixie/02-setting-up-k8s/02-eks-setup.md
@@ -26,19 +26,19 @@ If you don't have a cluster ready you can set one up based on the [Getting Start
 
 Create a cluster with managed node-pools using [eksctl](https://eksctl.io/usage/creating-and-managing-clusters/):
 
-```
+```bash
 eksctl create cluster
 ```
 
 Update kubeconfig to point to the right cluster:
 
-```
+```bash
 aws eks update-kubeconfig --name <cluster-name>
 ```
 
 Verify that you are pointing to the right cluster
 
-```
+```bash
 kubectl get svc
 ```
 
diff --git a/content/en/02-installing-pixie/02-setting-up-k8s/03-gke-setup.md b/content/en/02-installing-pixie/02-setting-up-k8s/03-gke-setup.md
@@ -21,27 +21,27 @@ Install [gcloud SDK](https://cloud.google.com/sdk/install)
 
 Install the `kubectl` by running:
 
-```
+```bash
 gcloud components install kubectl
 ```
 
 Set a default project:
 
-```
+```bash
 gcloud config set project project-id
 ```
 
 Set a default compute zone:
 
-```
+```bash
 gcloud config set compute/zone compute-zone
 ```
 
 ### Create the cluster
 
 Run the following command to create a 2 node cluster:
 
-```
+```bash
 gcloud container clusters create cluster-name --num-nodes=2 --machine-type=e2-standard-2
 ```
 
@@ -51,13 +51,13 @@ Please review, GCP's [docs](https://cloud.google.com/kubernetes-engine/docs/conc
 
 Once created, get authentication credentials:
 
-```
+```bash
 gcloud container clusters get-credentials cluster-name
 ```
 
 And, verify you have the intended nodes active:
 
-```
+```bash
 kubectl get nodes
 ```
 
diff --git a/content/en/02-installing-pixie/02-setting-up-k8s/04-aks-setup.md b/content/en/02-installing-pixie/02-setting-up-k8s/04-aks-setup.md
@@ -24,7 +24,7 @@ If you don't, follow the [AKS quick start](https://docs.microsoft.com/en-us/azur
 
 Run the following command to create a 2 node cluster:
 
-```
+```bash
 az aks create --resource-group myResourceGroup --name myAKSCluster --node-count 2 --enable-addons monitoring --generate-ssh-keys
 ```
 
@@ -34,13 +34,13 @@ Or, use the portal based on instructions [here](https://docs.microsoft.com/en-us
 
 Update kubeconfig to point to the right cluster:
 
-```
+```bash
 az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
 ```
 
 And, verify you have the intended nodes active:
 
-```
+```bash
 kubectl get nodes
 ```
 
diff --git a/content/en/02-installing-pixie/03-install-guides/01-community-cloud-for-pixie.md b/content/en/02-installing-pixie/03-install-guides/01-community-cloud-for-pixie.md
@@ -25,7 +25,7 @@ If you don't have a Kubernetes cluster available, you can set up Minikube as a l
 
 The easiest way to install Pixie's CLI is using the install script:
 
-``` bash
+```bash
 # Copy and run command to install the Pixie CLI.
 bash -c "$(curl -fsSL https://withpixie.ai/install.sh)"
 ```
@@ -46,7 +46,7 @@ To deploy Pixie using the CLI:
   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
+```bash
 # List Pixie deployment options.
 px deploy --help
 
@@ -117,7 +117,7 @@ kubectl get pods -n px-sock-shop
 
 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
+```bash
 # List built-in scripts
 px scripts list
 
diff --git a/content/en/02-installing-pixie/03-install-guides/02-self-hosted-pixie.md b/content/en/02-installing-pixie/03-install-guides/02-self-hosted-pixie.md
@@ -137,7 +137,7 @@ export PL_CLOUD_ADDR=dev.withpixie.dev
 
 The easiest way to install Pixie's CLI is using the install script:
 
-``` bash
+```bash
 # Copy and run command to install the Pixie CLI.
 bash -c "$(curl -fsSL https://withpixie.ai/install.sh)"
 ```
@@ -158,7 +158,7 @@ To deploy Pixie using the CLI:
   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
+```bash
 # Deploy the Pixie Platform in your K8s cluster (No OLM present on cluster).
 px deploy --dev_cloud_namespace plc
 
diff --git a/content/en/02-installing-pixie/04-install-schemes/01-cli.md b/content/en/02-installing-pixie/04-install-schemes/01-cli.md
@@ -19,7 +19,7 @@ You can install the CLI in one of four ways:
 
 ### Using the install script (easiest)
 
-``` bash
+```bash
 # Copy and run command to install the Pixie CLI.
 bash -c "$(curl -fsSL https://withpixie.ai/install.sh)"
 ```
@@ -35,7 +35,7 @@ bash -c "$(curl -fsSL https://withpixie.ai/install.sh)"
 
 Download the correct binary for your operating system and make it executable:
 
-``` bash
+```bash
 # Download the latest Pixie linux binary.
 curl -o px https://storage.googleapis.com/pixie-dev-public/cli/latest/cli_linux_amd64
 
@@ -53,7 +53,7 @@ mv px /usr/local/bin
 
 ### Using Docker
 
-``` bash
+```bash
 alias px="docker run -i --rm -v ${HOME}/.pixie:/root/.pixie pixielabs/px"
 ```
 
@@ -66,7 +66,7 @@ Download the assets:
 
 Install the Pixie package:
 
-``` bash
+```bash
 # Install Pixie .deb package.
 dpkg -i pixie-px.x86_64.deb
 ```
@@ -80,7 +80,7 @@ Download the assets:
 
 Install the Pixie package:
 
-``` bash
+```bash
 # Install Pixie .rpm package.
 rpm -i pixie-px.x86_64.rpm
 ```
@@ -95,7 +95,7 @@ rpm -i pixie-px.x86_64.rpm
   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
+```bash
 # List Pixie deployment options.
 px deploy --help
 
diff --git a/content/en/02-installing-pixie/04-install-schemes/02-yaml.md b/content/en/02-installing-pixie/04-install-schemes/02-yaml.md
@@ -41,7 +41,7 @@ Create a directory to save Pixie's manifest files and run the following CLI comm
   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
+```bash
 # Extract YAML (No OLM present on cluster).
 px deploy --extract_yaml <NAME_OF_PIXIE_YAMLS_FOLDER> --deploy_key <PIXIE_DEPLOYMENT_KEY>
 
@@ -59,7 +59,7 @@ px deploy --extract_yaml <NAME_OF_PIXIE_YAMLS_FOLDER> --deploy_key <PIXIE_DEPLOY
 
 Deploy Pixie in your target cluster by running:
 
-``` bash
+```bash
 # Deploy
 kubectl apply --recursive -f <NAME_OF_PIXIE_YAMLS_FOLDER>
 ```
@@ -74,7 +74,7 @@ For more deploy options that you can specify to configure Pixie, refer to our [d
 
 To verify that Pixie is running in your environment you can check the [admin page](https://work.withpixie.ai/admin) or run:
 
-``` bash
+```bash
 # Check pods are up
 kubectl get pods -n pl
 
diff --git a/content/en/02-installing-pixie/04-install-schemes/03-helm.md b/content/en/02-installing-pixie/04-install-schemes/03-helm.md
@@ -43,7 +43,7 @@ Deploy Pixie in your target cluster by running:
   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
+```bash
 # Add the Pixie operator chart.
 helm repo add pixie-operator https://pixie-operator-charts.storage.googleapis.com
 
@@ -70,7 +70,7 @@ For more deploy options that you can specify to configure Pixie, refer to our [d
 
 To verify that Pixie is running in your environment you can check the [admin page](https://work.withpixie.ai/admin) or run:
 
-``` bash
+```bash
 # Check pods are up
 kubectl get pods -n pl
 
diff --git a/content/en/04-tutorials/01-pixie-101/06-profiler.md b/content/en/04-tutorials/01-pixie-101/06-profiler.md
@@ -27,13 +27,13 @@ Java support is a beta feature available in Pixie vizier version 0.10.22+, and m
 
 To enable Java support when deploying Pixie with the [Pixie CLI](/installing-pixie/install-schemes/cli/), run:
 
-```
+```bash
 px deploy --pem_flags=PL_PROFILER_JAVA_SYMBOLS=1
 ```
 
 To enable Java support when deploying Pixie with [Helm](/installing-pixie/install-schemes/helm/), run:
 
-```
+```bash
 helm install pixie pixie-operator/pixie-operator-chart --set deployKey=<deploy-key-goes-here> --set clusterName=<cluster-name> --namespace pl --create-namespace --set dataCollectorParams.customPEMFlags.PL_PROFILER_JAVA_SYMBOLS=true
 ```
 
diff --git a/content/en/04-tutorials/04-custom-data/01-distributed-bpftrace-deployment.md b/content/en/04-tutorials/04-custom-data/01-distributed-bpftrace-deployment.md
@@ -166,7 +166,7 @@ Lines 55-69 query the collected data, convert known IPs to domain names, and gro
 
 If you'd like to filter the results to a particular service, modify line 67 to include the namespace:
 
-```
+```python
 df = df[px.contains(df['dst'], 'sock-shop')]
 ```
 
diff --git a/content/en/05-reference/01-admin/02-data-transfer-mode.md b/content/en/05-reference/01-admin/02-data-transfer-mode.md
@@ -43,7 +43,7 @@ To configure your cluster to use Data Isolation Mode, use Pixie's CLI tool to
 
 1. Get your Cluster ID:
 
-```
+```bash
 px get viziers
 ```
 
@@ -53,7 +53,7 @@ px get viziers
 
 2. Switch from Passthrough Mode (default) to Data Isolation Mode. Don't forget to copy in your Cluster ID.
 
-```
+```bash
 px config update -c <YOUR_CLUSTER_ID> --passthrough=false
 ```
 
@@ -67,7 +67,7 @@ Once enabled, the Live UI [Admin Page](https://work.withpixie.ai/admin) will sho
 
 To switch from Data Isolation (Direct) Mode to Passthrough Mode, run:
 
-```
+```bash
 px config update -c <YOUR_CLUSTER_ID> --passthrough=true
 ```
 
diff --git a/content/en/05-reference/01-admin/04-deploy-options.md b/content/en/05-reference/01-admin/04-deploy-options.md
@@ -44,7 +44,7 @@ When deploying Pixie, you have the option of adding one or more custom [labels](
 
 To label Pixie's resources when deploying with the [Pixie CLI](/installing-pixie/install-schemes/cli/), use the `--labels` flag:
 
-``` bash
+```bash
 px deploy --labels=key1=value1,key2=value2
 ```
 
@@ -87,7 +87,7 @@ The default memory limit is 2Gi per PEM. The lowest recommended value is [1Gi](/
 
 To set Pixie's memory limit when deploying with the [Pixie CLI](/installing-pixie/install-schemes/cli/), use the `--pem_memory_limit` flag:
 
-``` bash
+```bash
 px deploy --pem_memory_limit=1Gi
 ```
 
@@ -105,7 +105,7 @@ By default, the PEM's memory request will be the same as the limit. When deployi
 
 To set Pixie's memory request when deploying with the [Pixie CLI](/installing-pixie/install-schemes/cli/), use the `--pem_memory_request` flag:
 
-``` bash
+```bash
 px deploy --pem_memory_request=1Gi
 ```
 
@@ -121,7 +121,7 @@ This is an advanced option that most developers shouldn't need. For more discuss
 
 To set Pixie's data store memory limit when deploying with the [Pixie CLI](/installing-pixie/install-schemes/cli/), use the `--pem_flags` flag:
 
-``` bash
+```bash
 px deploy --pem_flags="PL_TABLE_STORE_DATA_LIMIT_MB=1000"
 ```
 
diff --git a/content/en/05-reference/01-admin/05-environment-configs.md b/content/en/05-reference/01-admin/05-environment-configs.md
@@ -25,7 +25,7 @@ If deploying Pixie through Helm, ensure you are setting `-set deployOLM=false` o
 
 OpenShift utilizes [SCCs](https://docs.openshift.com/container-platform/4.6/authentication/managing-security-context-constraints.html) to restrict pod actions and access. If your cluster is running a more restrictive set of SCCs, you will need to give Pixie privileged access.
 
-```
+```yaml
 kind: SecurityContextConstraints
 apiVersion:  security.openshift.io/v1
 metadata:
diff --git a/content/en/05-reference/01-admin/11-updating-pixie.md b/content/en/05-reference/01-admin/11-updating-pixie.md
@@ -57,6 +57,6 @@ kustomize build k8s/cloud/public/ | kubectl apply -f - --namespace=plc
 
 6. Update Pixie Vizier with:
 
-```
+```bash
 px update vizier
 ```
