Merge branch 'master' into staging

Author: Dlorite

.github/workflows/production.yml

@@ -18,6 +18,7 @@ jobs:
     # Steps represent a sequence of tasks that will be executed as part of the job
     steps:
     # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
+    - uses: actions/checkout@v2
     - name: Set up Python 3.10
       uses: actions/setup-python@v4
       with:

.github/workflows/productionDeploy.yml

@@ -28,4 +28,9 @@ jobs:
       with:
         cluster_name: ${{ secrets.CLUSTER_NAME }}
         location: 'us-central1-a'
-        project_id: ${{ secrets.PROJECT_ID }}
+        project_id: ${{ secrets.PROJECT_ID }}
+    - name: Deploy in production
+      run: |
+        chmod +x deployment/master/deploy.sh
+        sh ./deployment/master/deploy.sh
+

resources/ceph/INSTALL.md

@@ -9,5 +9,4 @@ Make sure that the Prometheus module is activated in the Ceph cluster by running
 ceph mgr module enable prometheus
 ```
 # Installation
-
 The application is ready to be scraped

resources/elasticsearch/INSTALL.md

@@ -22,7 +22,6 @@ kubectl create -n Your-Application-Namespace secret generic elastic-tls-secret \
   --from-file=root-ca.key=/path/to/tls/ca-key \
   --from-file=root-ca.pem=/path/to/tls/ca-pem
 ```
-
 # Installation
 
 You can use our helm-charts in order to install the exporter in your cluster.

resources/fluentd/INSTALL.md

@@ -34,7 +34,6 @@ As seen in the [official plugin documentation](https://github.com/fluent/fluent-
 ```
 
 If you are deploying Fluentd using the [official Helm chart](https://github.com/fluent/helm-charts/tree/main/charts/fluentd), it already has these plugins enabled by default in its configuration, so no additional actions are needed.
-
 # Installation
 
 The application is ready to be scraped

resources/keda/INSTALL.md

@@ -7,7 +7,6 @@ Make sure that the prometheus metrics are activated. If you install Keda with He
 ```
 --set prometheus.metricServer.enabled=true
 ```
-
 # Installation
 
 The application is ready to be scraped

resources/nginx-ingress/INSTALL.md

@@ -18,9 +18,6 @@ Another option is adding the following line to the NGINX Ingress configuration f
 ```
 controller.metrics.podAnnotations.prometheus.io/scrape=true
 ```
-
-
-
 # Installation
 
 The application is ready to be scraped

resources/nginx/README.md

@@ -12,4 +12,4 @@ The integration is using the following exporters:
 # Attributions
 The configuration files and dashboards maintained by [Sysdig team](https://sysdig.com/).
 # License
-- nginx-exporter with Apache license.
+- nginx-exporter with Apache license.

resources/openshift-haproxy-router/INSTALL.md

@@ -83,7 +83,6 @@ subjects:
   name: sysdig-agent
   namespace: sysdig-agent   # Remember to change to the namespace where you have the Sysdig agents deployed
 ```
-
 # Installation
 
 The application is ready to be scraped

resources/postgresql/INSTALL.md

@@ -78,9 +78,7 @@ kubectl create -n Your-Application-Namespace secret generic postgresql-exporter
   --from-literal=password=password \
   --from-file=sslRootCert=/path/to/tls/cert
 ```
-
 # Installation
-
 You can use our helm-charts in order to install the exporter in your cluster.
 ```sh
 helm install --repo https://sysdiglabs.github.io/integrations-charts postgresql-exporter postgresql-exporter