Bump version to 2.3.7

Chart.yaml

@@ -1,7 +1,7 @@
 name: trendmicro-container-security
 description: Trend Micro Cloud One Container Security
-appVersion: "2.3.6"
-version: "2.3.6"
+appVersion: "2.3.7"
+version: "2.3.7"
 kubeVersion: ">=1.16.0-0"
 apiVersion: v1
 deprecated: false

README.md

@@ -159,15 +159,15 @@ By default, Container Security Continuous Compliance will create a Kubernetes ne
 
 ### Install a specific version of the Container Security helm chart
 
-If you want to install a specific version you can use the archive link for the tagged release. For example, to install Trend Micro Cloud One Container Security helm chart version 2.3.6, run the following command:
+If you want to install a specific version you can use the archive link for the tagged release. For example, to install Trend Micro Cloud One Container Security helm chart version 2.3.7, run the following command:
 
 ```sh
   helm install \
     --values overrides.yaml \
     --namespace ${namespace} \
     --create-namespace \
     trendmicro \
-    https://github.com/trendmicro/cloudone-container-security-helm/archive/2.3.6.tar.gz
+    https://github.com/trendmicro/cloudone-container-security-helm/archive/2.3.7.tar.gz
 ```
 
 ### Enabling or disabling a specific component

values.yaml

@@ -508,7 +508,7 @@ images:
 
     ## Default tag for images to pull. This can be overridden for each image
     ## by specifying the tag attribute at the image level.
-    tag: 2.3.6
+    tag: 2.3.7
 
     ## Default pull policy for images. This can be overridden for each image
     ## by specifying the pullPolicy attribute at the image level.
@@ -523,7 +523,7 @@ images:
     # imagePullSecret:
   admissionController:
     repository: admission-controller
-    digest: sha256:dae83b967119c3aa8510c8255b52b434b5d6be2f0dc43fea3fbec142c40059dd
+    digest: sha256:f4400eb108419c5137b88d5616e6f4699548930ef587867198226bc766c08079
 
   oversight:
     repository: oversight-controller
@@ -547,15 +547,15 @@ images:
 
   scanManager:
     repository: scan-manager
-    digest: sha256:7bc1972f0573ce4238c5cc8bfea81efaba4c9be6488f4d926e9eca8428de1cd2
+    digest: sha256:f6691b2419219f3f850275b1c2d8da0da6c02210383775382660ac0c0870a54d
 
   scanJob:
     repository: scan-job
     digest: sha256:6e7e891a36e86f0b5f21ce18a031783a8fe969560730676a6bf58ed2390cbbc6
 
   workloadOperator:
     repository: workload-operator
-    digest: sha256:417c21098f381c7b18b719490cf70c472cd9e845f532dc16b5ad14c237c5ada1
+    digest: sha256:5e7b9f2d06da46e3e0dfad95d5ea04fa49ea4a9332d1446268bc5379e55d1ccd
 ##
 ## Determine whether to use existing secrets in the target namespace rather than
 ## specifying in overrides.yaml. Useful if you want to manage secrets on your own, e.g., in argocd.