Skip to content

docs: require k8s-bake v4.1.1+ in the bake example #555

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
David Gamero (davidgamero) merged 1 commit into from
Aug 11, 2026
+8 −1
Merged

docs: require k8s-bake v4.1.1+ in the bake example #555

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
9 changes: 8 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -439,6 +439,13 @@ jobs:

### Use bake action to get manifests deploying to a Kubernetes cluster

> **Requires `azure/k8s-bake@v4.1.1` or later.** Since v7, `k8s-deploy` rejects
> `manifests:` paths that resolve outside `GITHUB_WORKSPACE`. Earlier versions of
> `k8s-bake` wrote the baked manifest to `RUNNER_TEMP`, which is a sibling of the
> workspace on hosted runners, so `manifestsBundle` was rejected. `k8s-bake` v4.1.1
> writes into the workspace instead ([Azure/k8s-bake#289](https://github.com/Azure/k8s-bake/pull/289)).
> Workflows that pass `manifestsBundle` need no other changes.

```yaml
on: [push]
env:
Expand Down Expand Up @@ -473,7 +480,7 @@ jobs:
container-registry-password: ${{ secrets.REGISTRY_PASSWORD }}
secret-name: demo-k8s-secret

- uses: azure/k8s-bake@v3
- uses: azure/k8s-bake@v4
with:
renderEngine: 'helm'
helmChart: './aks-helloworld/'
Expand Down
Loading