Fix deepfence agent privileges on security hardened clusters (#2314)

Author: ramanan-ravi

deployment-scripts/helm-charts/deepfence-agent/Chart.yaml

@@ -15,7 +15,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 2.3.1
+version: 2.3.2
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

deployment-scripts/helm-charts/index.yaml

@@ -1,6 +1,16 @@
 apiVersion: v1
 entries:
   deepfence-agent:
+  - apiVersion: v2
+    appVersion: 2.3.1
+    created: "2024-09-23T13:28:28.614763+05:30"
+    description: Deepfence Agent - Helm chart for Kubernetes
+    digest: f372335ff0388536ce2bec841d83e9b70e3de545aba4f7f402641e6a651c6fcd
+    name: deepfence-agent
+    type: application
+    urls:
+    - deepfence-agent-2.3.2.tgz
+    version: 2.3.2
   - apiVersion: v2
     appVersion: 2.3.1
     created: "2024-09-11T18:40:38.594491+05:30"
@@ -783,4 +793,4 @@ entries:
     urls:
     - deepfence-router-1.0.0.tgz
     version: 1.0.0
-generated: "2024-09-11T18:40:38.593973+05:30"
+generated: "2024-09-23T13:28:28.614265+05:30"