Skip to content

Commit

Permalink
Sync appVersion: 0.27.0
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] committed Nov 5, 2024
1 parent a315697 commit fe5e7d5
Show file tree
Hide file tree
Showing 6 changed files with 19 additions and 7 deletions.
6 changes: 6 additions & 0 deletions charts/agent-docker/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions charts/agent-docker/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion charts/agent-docker/README.md
Original file line number Diff line number Diff line change
@@ -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.
Expand Down
6 changes: 6 additions & 0 deletions charts/agent-k8s/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
4 changes: 2 additions & 2 deletions charts/agent-k8s/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions charts/agent-k8s/README.md
Original file line number Diff line number Diff line change
@@ -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.
Expand Down Expand Up @@ -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:

Expand Down

0 comments on commit fe5e7d5

Please sign in to comment.