Skip to content

Sync base-images v1.3.10, Go 1.26.5, lib-helm 1.72.10#105

Merged
duckhawk merged 3 commits into
mainfrom
chore/sync-tooling-1.3.10-lib-1.72.10-202607170634
Jul 20, 2026
Merged

Sync base-images v1.3.10, Go 1.26.5, lib-helm 1.72.10#105
duckhawk merged 3 commits into
mainfrom
chore/sync-tooling-1.3.10-lib-1.72.10-202607170634

Conversation

@duckhawk

Copy link
Copy Markdown
Member

Description

Automated tooling sync for snapshot-controller (scheduled sync_storage_modules_tooling.py).

  • BASE_IMAGES_VERSION: v1.3.2v1.3.10 in .github/workflows/*.yml.
  • Go: go directive already 1.26.5 in scanned api/, images/ and hooks/ modules.
  • lib-helm: replace chart bundle with deckhouse_lib_helm-1.72.10.tgz (previous: 1.72.9).

Why do we need it, and what problem does it solve?

Keeps the module aligned with the latest deckhouse/container-base/base-images release and deckhouse/lib-helm
so CI and image builds use current base image digests, Go toolchain version, and Helm library charts.

What is the expected result?

  • Pipelines resolve BASE_IMAGES_VERSION to the new (or current) tag and download matching base_images.yml.
  • Go code under api/, images/ and hooks/ declares the same Go version as the default golang toolchain in base_images.yml.
  • charts/ contains the current deckhouse_lib_helm-*.tgz when an update was required.

Checklist

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

- BASE_IMAGES_VERSION -> v1.3.10
- charts/deckhouse_lib_helm-1.72.10.tgz
fastrapier
fastrapier previously approved these changes Jul 20, 2026
duckhawk added 2 commits July 20, 2026 12:32
Trivy flagged two fixable golang.org/x CVEs across the module's Go
binaries (go-hooks, webhooks) and the vendored external-snapshotter
driver:

- golang.org/x/net CVE-2026-46600 — parsing an invalid SVCB or HTTPS RR
  can panic in golang.org/x/net/dns/dnsmessage (fixed in v0.56.0).
- golang.org/x/text CVE-2026-56852 — infinite loop on invalid input
  (fixed in v0.39.0).

Bump both (with the transitive x/crypto/x/sys/x/sync/x/term bumps they
pull) in hooks/go and images/webhooks go.mod, and retarget
images/snapshot-controller/patches/003-fix-cve-golang-x.patch to ship the
same versions in the external-snapshotter driver tree. All our-code
binaries build clean; the full patch set 001-003 applies to a fresh
v8.5.0 checkout and 'make build' succeeds in module mode.

Signed-off-by: v.oleynikov <vasily.oleynikov@flant.com>
golang.org/x/crypto GO-2026-5932 (the openpgp subpackage is unmaintained
and unsafe) has no fixed release and is reported against both the go-hooks
binary embedded in the bundle image and the external-snapshotter driver
binary. The openpgp package is not used in either: in go-hooks x/crypto is
pulled in only for its ocsp package (020-webhook-certs -> module-sdk
tls-certificate -> cloudflare/cfssl/helpers), and in the snapshot-controller
driver only for cryptobyte (k8s.io/apiserver/pkg/server); `go mod why
golang.org/x/crypto/openpgp` reports the main module does not need it in
either binary, so it is not compiled in.

Add OpenVEX statements (status not_affected, justification
vulnerable_code_not_in_execute_path) for the bundle (repo-root
known_vulnerabilities.vex) and the snapshot-controller image
(images/snapshot-controller/known_vulnerabilities.vex), and wire the
existing "vex mitigation" template for both so cosign attaches them as
attestations trivy honours. Exclude *-vex-artifact images from
images-digests.yaml so the attestation carriers are not themselves
published or re-scanned.

Signed-off-by: v.oleynikov <vasily.oleynikov@flant.com>
@duckhawk
duckhawk merged commit 7d62907 into main Jul 20, 2026
13 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.

2 participants