Skip to content
This repository has been archived by the owner on Apr 2, 2024. It is now read-only.

Update chart appVersion to v0.1.166 #57

Merged
merged 1 commit into from
Sep 13, 2023
Merged

Update chart appVersion to v0.1.166 #57

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions charts/enforce-agent/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.65
appVersion: v0.1.165
version: 0.0.66
appVersion: v0.1.166
keywords:
- chainguard
home: https://chainguard.dev
Expand Down
3 changes: 2 additions & 1 deletion charts/enforce-agent/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

<!-- This README.md is generated. Please edit README.md.gotmpl -->

![Version: 0.0.64](https://img.shields.io/badge/Version-0.0.64-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v0.1.165](https://img.shields.io/badge/AppVersion-v0.1.165-informational?style=flat-square)
![Version: 0.0.66](https://img.shields.io/badge/Version-0.0.66-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v0.1.166](https://img.shields.io/badge/AppVersion-v0.1.166-informational?style=flat-square)

A helm chart for Chainguard's Enforce Agent.

Expand Down Expand Up @@ -42,5 +42,6 @@ helm uninstall [RELEASE_NAME]
| clusterName | string | `""` | |
| enforcerOptions.enableCIPCache | bool | `false` | |
| enforcerOptions.namespaceEnforcementMode | string | `"opt-in"` | |
| enforcerOptions.noMatchPolicy | string | `"deny"` | |
| enforcerOptions.webhookFailOpen | bool | `false` | |
| inviteCode | string | `""` | Invite code assigned to group where clusters will be registered. This can be generated with: `chainctl iam invite create $GROUP --cluster -ojson | jq -r .code` |
4 changes: 2 additions & 2 deletions charts/enforce-agent/templates/enforce-agent.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -314,7 +314,7 @@ spec:
serviceAccountName: controller
containers:
- name: controller
image: us.gcr.io/prod-enforce-fabc/controlplane:v0.1.165@sha256:755d2568be8b5a6afd2a76884e0adfa4c7e51aee096837de7987d4f2bc1ec5f2
image: us.gcr.io/prod-enforce-fabc/controlplane:v0.1.166@sha256:3c683150fab198c215a391a0de4ae09d5c1aa624cc10c430427fa97897edac36
resources:
requests:
cpu: 50m
Expand Down Expand Up @@ -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.165@sha256:ccf55bbdd980a988c9d6830c1a6d94d715b48135c8123e4105e5b2d31df8201f
image: us.gcr.io/prod-enforce-fabc/chainctl:v0.1.166@sha256:406a6f2dcac5e021cc39fef835985b5cabb1bd39ce6466c96ea114fdfa4fe1ac
readinessProbe:
exec:
command:
Expand Down