Helm is needed to support Observability

operations/observability/mixins/README.md

@@ -299,7 +299,10 @@ There are a couple of ways to trigger a werft job that will deploy a preview env
 
 1. You can open a Pull Request with the following line in the description:
 ```
-/werft with-observability
+# we deploy using K8s manifests generated by our new installer
+# observability only works with our old helm chart
+# to support observability, use with-helm will;
+/werft with-observability with-helm
 
 # Just in case your PR requires extra configuration on Prometheus side
 # (and you have a new branch on https://github.com/gitpod-io/observability with such changes)
@@ -309,13 +312,13 @@ There are a couple of ways to trigger a werft job that will deploy a preview env
 
 2. After opening a Pull Request, you can add a Github comment:
 ```
-/werft run with-observability
-/werft run withObservabilityBranch="<my-branch>"
+/werft run with-observability with-helm
+/werft run withObservabilityBranch="<my-branch>" with-observability
 ```
 
 3. Inside your workspace, run:
 ```
-werft run github -a with-observability="" -a withObservabilityBranch="<my-branch>"
+werft run github -a with-observability=true -a withObservabilityBranch="<my-branch>" -a with-helm=true
 ```
 
 As mentioned in [How is our mixin consumed?](#How-is-our-mixin-consumed), please remember that a commit must be done for us to update monitoring-satellite with the dashboards/alerts/recording rule changes.