Skip to content

Publish the Kubernetes credential provider image in releases - #44

Merged
EItanya merged 1 commit into
mainfrom
fix/release-credential-provider
Sep 18, 2026
Merged

EItanya merged 1 commit into
mainfrom
fix/release-credential-provider

Conversation

@EItanya

@EItanya EItanya commented Sep 18, 2026

Copy link
Copy Markdown

The chart now always deploys the Kubernetes credential provider, but the release workflow omitted its image. Add cmd/credential-provider/kubernetes-secrets to the existing build loop and publish it as ghcr.io/<owner>/<repo>/kubernetes-secrets:<tag>, matching the chart and installer. It receives the same release tags and Linux amd64/arm64 platforms as the other components.

Validation: both platform images build successfully with ko build --push=false; a dry run of the workflow step verifies all eight image paths, tags, and platforms; env -u NO_COLOR make verify passes.

Build the nested provider package with the release images and publish it under the kubernetes-secrets basename expected by the Helm chart.

Signed-off-by: Eitan Yarmush <eitan.yarmush@solo.io>
@EItanya
EItanya merged commit a7701e8 into main Sep 18, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant