diff --git a/charts/enforce-agent/Chart.yaml b/charts/enforce-agent/Chart.yaml index b04a7f0..ce1b9b5 100644 --- a/charts/enforce-agent/Chart.yaml +++ b/charts/enforce-agent/Chart.yaml @@ -8,8 +8,8 @@ description: | Documentation for the chart can be found [here](https://edu.chainguard.dev/chainguard/chainguard-enforce/chainguard-enforce-kubernetes/alternative-installation-methods/). type: application -version: 0.0.88 -appVersion: v0.1.190 +version: 0.0.89 +appVersion: v0.1.191 keywords: - chainguard home: https://chainguard.dev diff --git a/charts/enforce-agent/README.md b/charts/enforce-agent/README.md index 7fe0566..2c02f6e 100644 --- a/charts/enforce-agent/README.md +++ b/charts/enforce-agent/README.md @@ -2,7 +2,7 @@ -![Version: 0.0.88](https://img.shields.io/badge/Version-0.0.88-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v0.1.190](https://img.shields.io/badge/AppVersion-v0.1.190-informational?style=flat-square) +![Version: 0.0.89](https://img.shields.io/badge/Version-0.0.89-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v0.1.191](https://img.shields.io/badge/AppVersion-v0.1.191-informational?style=flat-square) A helm chart for Chainguard's Enforce Agent. diff --git a/charts/enforce-agent/templates/enforce-agent.yaml b/charts/enforce-agent/templates/enforce-agent.yaml index 86a8654..81edd67 100644 --- a/charts/enforce-agent/templates/enforce-agent.yaml +++ b/charts/enforce-agent/templates/enforce-agent.yaml @@ -314,7 +314,7 @@ spec: serviceAccountName: controller containers: - name: controller - image: us.gcr.io/prod-enforce-fabc/controlplane:v0.1.190@sha256:26ae4a2d57c6abb0e2d0c3485c147b8e7a63568d4c5004eb1168095987917f80 + image: us.gcr.io/prod-enforce-fabc/controlplane:v0.1.191@sha256:0e4ce893f191cacca5359b41758e876b6e7f0833c0ca50d92cd6f84599db0ce5 resources: requests: cpu: 50m @@ -388,7 +388,7 @@ spec: # The STS container is responsible for normalizing federated OIDC # tokens by using `chainctl auth login [...] --refresh` with the # "sts-in" identity token. - image: us.gcr.io/prod-enforce-fabc/chainctl:v0.1.190@sha256:ea4c53f2ea4923a8ca4cb82ac6417369a10215f30b9ffafdf36aa8680d81b0d2 + image: us.gcr.io/prod-enforce-fabc/chainctl:v0.1.191@sha256:f9288450d7441c6323264a445105ca7e932b5413af645800257fae23e6ea674f readinessProbe: exec: command: