diff --git a/charts/agent-docker/CHANGELOG.md b/charts/agent-docker/CHANGELOG.md
index f58b86a..c472a89 100644
--- a/charts/agent-docker/CHANGELOG.md
+++ b/charts/agent-docker/CHANGELOG.md
@@ -9,6 +9,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [UNRELEASED]
 
+## [v0.5.22]
+
+### Updated
+
+- Bumping chart version to v0.5.22 for scalr-agent v0.27.0
+
 ## [v0.5.21]
 
 ### Updated
diff --git a/charts/agent-docker/Chart.yaml b/charts/agent-docker/Chart.yaml
index da719ab..013ebb7 100644
--- a/charts/agent-docker/Chart.yaml
+++ b/charts/agent-docker/Chart.yaml
@@ -5,8 +5,8 @@ description: |
   where runs are executed in [dind](https://hub.docker.com/_/docker) sidecar container.
   Run phases are isolated into docker containers.
 type: application
-version: 0.5.21
-appVersion: 0.26.1
+version: 0.5.22
+appVersion: 0.27.0
 home: https://github.com/Scalr/agent-helm/tree/master/charts/agent-docker
 maintainers:
   - name: scalr
diff --git a/charts/agent-docker/README.md b/charts/agent-docker/README.md
index 44fa84e..e06d022 100644
--- a/charts/agent-docker/README.md
+++ b/charts/agent-docker/README.md
@@ -1,6 +1,6 @@
 # agent-docker
 
-![Version: 0.5.21](https://img.shields.io/badge/Version-0.5.21-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 0.26.1](https://img.shields.io/badge/AppVersion-0.26.1-informational?style=flat-square)
+![Version: 0.5.22](https://img.shields.io/badge/Version-0.5.22-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 0.27.0](https://img.shields.io/badge/AppVersion-0.27.0-informational?style=flat-square)
 
 A Helm chart for the scalr-agent deployment on ths Kubernetes cluster,
 where runs are executed in [dind](https://hub.docker.com/_/docker) sidecar container.
diff --git a/charts/agent-k8s/CHANGELOG.md b/charts/agent-k8s/CHANGELOG.md
index 16a79fd..79e6e9a 100644
--- a/charts/agent-k8s/CHANGELOG.md
+++ b/charts/agent-k8s/CHANGELOG.md
@@ -9,6 +9,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [UNRELEASED]
 
+## [v0.5.22]
+
+### Updated
+
+- Bumping chart version to v0.5.22 for scalr-agent v0.27.0
+
 ### Added
 
 - Added `restrictMetadataService` option. When set to true, applies pod network policy that blocks outbound access to instance metadata service.
diff --git a/charts/agent-k8s/Chart.yaml b/charts/agent-k8s/Chart.yaml
index ee4bceb..038e56d 100644
--- a/charts/agent-k8s/Chart.yaml
+++ b/charts/agent-k8s/Chart.yaml
@@ -10,8 +10,8 @@ description: |
   > It has many advantages over the [`agent-docker`](/charts/agent-docker) chart and
   > would eventually replace it.
 type: application
-version: 0.5.21
-appVersion: 0.26.1
+version: 0.5.22
+appVersion: 0.27.0
 home: https://github.com/Scalr/agent-helm/tree/master/charts/agent-k8s
 maintainers:
   - name: scalr
diff --git a/charts/agent-k8s/README.md b/charts/agent-k8s/README.md
index 263a36c..738e37d 100644
--- a/charts/agent-k8s/README.md
+++ b/charts/agent-k8s/README.md
@@ -1,6 +1,6 @@
 # agent-k8s
 
-![Version: 0.5.21](https://img.shields.io/badge/Version-0.5.21-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 0.26.1](https://img.shields.io/badge/AppVersion-0.26.1-informational?style=flat-square)
+![Version: 0.5.22](https://img.shields.io/badge/Version-0.5.22-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 0.27.0](https://img.shields.io/badge/AppVersion-0.27.0-informational?style=flat-square)
 
 A Helm chart for the scalr-agent deployment on the Kubernetes cluster,
 where runs are executed in Pods in the same cluster.
@@ -109,7 +109,7 @@ as its data home.
 
 ## Restrict Access to VM Metadata Service
 
-The chart includes an optional feature to restrict the pods from accessing the VM metadata service at 169.254.169.254, which is common for both AWS and GCP environments.
+The chart includes an optional feature to restrict the pods from accessing the VM metadata service at 169.254.169.254, that is common for both AWS and GCP environments.
 
 To enable it, use the `restrictMetadataService` option: