chore(deps): update dependency viaduct-ai/kustomize-sops to v4.5.1 #35
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/viaduct-ai-kustomize-sops-4.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v4.4.0->v4.5.1Release Notes
viaduct-ai/kustomize-sops (viaduct-ai/kustomize-sops)
v4.5.1Compare Source
Upgrade Guide: v4.5.0 to v4.5.1
What changed
In v4.5.0,
ksops installalways copied bothksopsandkustomizefrom hardcoded paths. This release makes two improvements based on community feedback (#327):ksops installnow usesos.Executable()to resolve its own binary path instead of hardcoding/usr/local/bin/ksops. This makes the install command work regardless of where the binary is located.Kustomize copying is now opt-in via
--with-kustomize. Since ArgoCD already ships with kustomize,ksops installnow only copies theksopsbinary by default. Pass--with-kustomizeto also copy kustomize.How to upgrade
Add
--with-kustomizeto yourksops installcommand if you want to continue overriding ArgoCD's built-in kustomize (the previous default behavior).Before:
After:
If you don't need to override ArgoCD's kustomize, you can drop
--with-kustomizeand remove the kustomize volume mount:Changelog
fd75a70fix: use os.Executable() for install and make kustomize opt-in (#330)d9442dcv4.5.1v4.5.0Compare Source
Upgrade Guide: ArgoCD Init Container
What changed
Starting in v4.4.0, the ksops Docker image uses a distroless base image, which does not include /bin/sh, mv, or other shell utilities. This broke the documented ArgoCD init container pattern that relied on shell commands to copy binaries into a shared volume.
This release adds a built-in ksops install subcommand that copies the ksops and kustomize binaries to a target directory — no shell required.
How to upgrade
Replace the command and args in your init container. The volume mounts stay the same.
Before:
After:
That's it. No other changes to your volumes, volume mounts, or container definitions are needed.
Affected configurations
This applies to all three documented ArgoCD integration methods:
Workarounds no longer needed
If you were using any of these workarounds, you can remove them:
Changelog
92bc163chore(deps): bump actions/checkout from 5 to 6 (#307)42d7795chore(deps): bump actions/setup-go from 5 to 6 (#302)cfb835cchore(deps): bump docker/login-action from 3 to 4 (#315)a25bfcdchore(deps): bump docker/setup-buildx-action from 3 to 4 (#316)2aee20echore(deps): bump docker/setup-qemu-action from 3 to 4 (#317)061495fchore(deps): bump filippo.io/edwards25519 from 1.1.0 to 1.1.1 (#309)845389achore(deps): bump github.com/aws/aws-sdk-go-v2/service/s3 (#325)d70b62echore(deps): bump github.com/getsops/sops/v3 from 3.11.0 to 3.12.2 (#319)98fe884chore(deps): bump github.com/go-jose/go-jose/v4 from 4.1.1 to 4.1.4 (#323)80616dechore(deps): bump github/codeql-action from 3 to 4 (#305)eb80fe6chore(deps): bump go.opentelemetry.io/otel/sdk from 1.37.0 to 1.43.0 (#326)dd0987echore(deps): bump golang.org/x/crypto from 0.42.0 to 0.45.0 (#306)31dfb4echore(deps): bump google.golang.org/grpc from 1.75.1 to 1.79.3 (#318)d4c8c13chore(deps): bump goreleaser/goreleaser-action from 6 to 7 (#312)dfeab3fchore: v4.5.0 (#329)8f3b8d1feat: addksops installsubcommand for distroless compatibility (#327)50ad78ffeat: concurrent secret decryption (#328)4345f5ffix: pin to 1.25.08624cb3update(sops): 3.10.2 -> 3.11.0 (#304)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.