diff --git a/charts/enforce-agent/Chart.yaml b/charts/enforce-agent/Chart.yaml index 4b0ccf1..d94fb39 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.69 -appVersion: v0.1.169 +version: 0.0.70 +appVersion: v0.1.170 keywords: - chainguard home: https://chainguard.dev diff --git a/charts/enforce-agent/README.md b/charts/enforce-agent/README.md index b861c9e..4ea97fb 100644 --- a/charts/enforce-agent/README.md +++ b/charts/enforce-agent/README.md @@ -2,7 +2,7 @@ -![Version: 0.0.69](https://img.shields.io/badge/Version-0.0.69-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v0.1.169](https://img.shields.io/badge/AppVersion-v0.1.169-informational?style=flat-square) +![Version: 0.0.70](https://img.shields.io/badge/Version-0.0.70-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v0.1.170](https://img.shields.io/badge/AppVersion-v0.1.170-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 98dccfb..9a5ca11 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.169@sha256:77a709ee5c9ed07e9f1ac2a4a444f608596d67f1b463814c0480d331c94ff3b8 + image: us.gcr.io/prod-enforce-fabc/controlplane:v0.1.170@sha256:ae3c6db1c599341eceb10fe5b2fa56e06eec9aae7de8f2fc674ce34ba5949300 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.169@sha256:96c0aa88da3d0d21b65e5a3bfd0819758dfa7518451fae804aaadafe3068257e + image: us.gcr.io/prod-enforce-fabc/chainctl:v0.1.170@sha256:63190b6f3258256b0221ecb685c4d6bd26cd43350683a0b963453684cfec4c9a readinessProbe: exec: command: