Merge branch 'main' into receivers-update

Author: merll

docs/for-ops/how-to/use-team-admin.md

@@ -84,12 +84,12 @@ Let's now configure public exposure for the workload we deployed in the namespac
 
 4. Fill in the port of the service (8080 in this case).
 
-5. Under `Exposure Ingress`, select `Ingress`.
+5. Under `Exposure Ingress`, select `External`.
 
 6. Turn off `Use team domain` and fill in the name of the service as the hostname (hello-deploy in this example).
 
 7. Click on `Submit`.
 
 8. Click on `Deploy Changes` (the Deploy Changes button in the left panel will light-up after you click on submit).
 
-Your service and URL will now show up in the list of Services.
+Your service and URL will now show up in the list of Services.

docs/get-started/labs/auto-image-update.md

@@ -59,7 +59,7 @@ Now go to the `green` repo in Gitea and change the the welcome message:
     <style>
       body {
         color: #ffffff;
-        background-color: green
+        background-color: green;
         font-family: Arial, sans-serif;
         font-size: 14px;
       }

docs/get-started/labs/canary-deployment.md

@@ -63,7 +63,7 @@ We now created 2 deployments. One for `blue` and one for `green`. The `green` im
 
 - Under `Traffic Control` click `enabled` (and use the default weights for v1 and v2).
 
-- Under `Exposure Ingress`, select `Ingress` and use the default configuration.
+- Under `Exposure Ingress`, select `External` and use the default configuration.
 
 - Click `Submit`.
 

docs/get-started/labs/create-netpols.md

@@ -79,6 +79,10 @@ Use the `k8s-deployment` chart to deploy the vote app. Use the following values:
 Name: `vote`
 
 ```yaml
+image:
+  repository: harbor.<your-domain>/team-<team-name>/vote
+  pullPolicy: IfNotPresent
+  tag: latest
 containerPorts:
   - name: http
     containerPort: 80
@@ -96,6 +100,10 @@ Use the `k8s-deployment` chart to deploy the worker app. Use the following value
 Name: `worker`
 
 ```yaml
+image:
+  repository: harbor.<your-domain>/team-<team-name>/worker
+  pullPolicy: IfNotPresent
+  tag: latest
 containerPorts:
   - name: http
     containerPort: 80
@@ -129,6 +137,10 @@ Use the `k8s-deployment` chart to deploy the result app. Use the following value
 Name: `result`
 
 ```yaml
+image:
+  repository: harbor.<your-domain>/team-<team-name>/result
+  pullPolicy: IfNotPresent
+  tag: latest
 containerPorts:
   - name: http
     containerPort: 80
@@ -239,10 +251,10 @@ curl https://apl-docs.net
 ```
 You should see the HTML of the apl-docs.net website
 
-2. Run the following command to see the `<h1>Build, Deploy and Run applications at scale</h1>` message:
+2. Run the following command to see the `<title data-rh="true">App Platform for LKE</title>` message:
 
 ```shell
-curl https://apl-docs.net | grep -o '<h1>.*</h1>'
+curl -s https://apl-docs.net | grep -o '<title.*</title>'
 ```
 
 3. Type `exit` to exit the Netshoot pod.

docs/get-started/labs/create-rabbitmq-cluster.md

@@ -78,13 +78,13 @@ In this example the `rabbitMQ cluster` was created in the Team demo, so we have
 1. Use the following command to retrieve the username:
 
 ```bash
-kubectl get secret rabbit1-rabbitmq-default-user -n team-demo -o jsonpath="{.data.username}" | base64 --decode
+kubectl get secret rabbit1-quickstart-rabbitmq-default-user -n team-demo -o jsonpath="{.data.username}" | base64 --decode
 ```
 
 2. Use the following command to retrieve the password:
 
 ```bash
-kubectl get secret rabbit1-rabbitmq-default-user -n team-demo -o jsonpath="{.data.password}" | base64 --decode
+kubectl get secret rabbit1-quickstart-rabbitmq-default-user -n team-demo -o jsonpath="{.data.password}" | base64 --decode
 ```
 :::info
 Make sure you don't copy the `%` symbol at the end.
@@ -129,13 +129,13 @@ To connect to the `rabbitMQ cluster` you use `AMQP` to open a connection. To ope
 1. Get the host use the following command:
 
 ```bash
-kubectl get secret rabbit1-rabbitmq-default-user -n team-demo -o jsonpath="{.data.host}" | base64 --decode
+kubectl get secret rabbit1-quickstart-rabbitmq-default-user -n team-demo -o jsonpath="{.data.host}" | base64 --decode
 ```
 
 2. Get the port use the following command:
 
 ```bash
-kubectl get secret rabbit1-rabbitmq-default-user -n team-demo -o jsonpath="{.data.port}" | base64 --decode
+kubectl get secret rabbit1-quickstart-rabbitmq-default-user -n team-demo -o jsonpath="{.data.port}" | base64 --decode
 ```
 
 The connection string is build like this:

docs/get-started/labs/create-sealed-secrets.md

@@ -4,7 +4,7 @@ title: Create Sealed Secrets
 sidebar_label: Create Sealed Secrets
 ---
 
-In this lab we will create sealed secrets and see how to securely sensitive information in git repository.
+In this lab we will create sealed secrets and see how to securely store sensitive information in git repository.
 
 ## Creating a Sealed Secret
 

docs/get-started/labs/create-workloads.md

@@ -36,7 +36,7 @@ image:
 
 All the needed Argo CD resources to deploy your workload will now be created. 
 
-8. Click on `Workloads` in the left menu. You will now see a list of all Workloads and there status:
+8. Click on `Workloads` in the left menu. You will now see a list of all Workloads and their status:
 
 ![workloads](../../img/workloads-2.png)
 

docs/get-started/labs/custom-metrics.md

@@ -72,7 +72,7 @@ for i in {1..1000}; do curl https://custom-metrics-labs.<your-domain>/hello; sle
 
 4. Click `+ Add visualization`.
 
-5. In the `Query` tab select `Prometheus Platform`.
+5. In the `Data source` tab select `Prometheus Platform`.
 
 6. In the `A` collapsible section, select a metric from the `Metric` drop-down list. In our example we use the `application_greetings_total` metric.
 
@@ -115,7 +115,7 @@ data:
 
 7. Click on `Dashboard settings` (in the top right).
 
-8. In the left menu click `JSON model`.
+8. Go to `JSON model` tab.
 
 9. Copy the JSON model and paste it into the ConfigMap. Make sure to indent with 4.
 

docs/get-started/labs/detect-threats.md

@@ -31,7 +31,7 @@ helm install team-labs falcosecurity/event-generator -n team-labs
 
 1. In the left menu, click on `Apps` and open `Grafana`.
 
-2. Click on the `Detected threads in containers` dashboards
+2. Click on the `Detected threats in containers` dashboards
 
 3. See all the generated threat events
 

docs/get-started/labs/using-argo-cd.md

@@ -74,7 +74,7 @@ Let's demonstrate the capabilities of Argo CD by adding some manifests to the re
 
 3. Commit the changes to the repository.
 
-Once you return to the Argo CD application, click on the `team<name>` application.
+Once you return to the Argo CD application, click on the `team-<name>` application.
 
 The application is set to sync automatically, so a manual `SYNC` is not required. Once ArgoCD completes the sync, the nginx deployment will appear as shown below:
 

docs/get-started/labs/view-metrics.md

@@ -28,7 +28,7 @@ The dashboards are dynamically added based on the enabled platform capabilities:
 | Kubernetes / Pods       | When Prometheus on the platform level is enabled |
 | Team status             | When Prometheus on the platform level is enabled |
 | Container scan results  | When Trivy Operator on the platform level is enabled |
-| Detected threads in containers | When Falco on the platform level is enabled |
+| Detected threats in containers | When Falco on the platform level is enabled |
 
 ## View container metrics