Repository navigation
feat(misc/hard): address security PR misc hard - #1443
Merged
Merged
Conversation
leninmehedy
approved these changes
Oct 26, 2026
Signed-off-by: Artur Reznikov <artur.reznikov@swirldslabs.com>
Signed-off-by: Artur Reznikov <artur.reznikov@swirldslabs.com>
Signed-off-by: Artur Reznikov <artur.reznikov@swirldslabs.com>
arturre
force-pushed
the
feat/1283-hard-misc
branch
from
October 27, 2026 18:29
c5f59e6 to
2fe2955
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
keysprojected volume,grpc-tls-key) now mount with mode0440instead of0644. ConfigMap volumes andgrpc-tls-certstay at0644. To keep the keys readable by the non-root node user (uid/gid 2000), the pod now getsfsGroup: 2000whenever Secret-backed keys are mounted. PreviouslyfsGroupwas set only when a Cheetah uploader was enabled.fsGroupChangePolicy: OnRootMismatchavoids re-chowning large PVCs on every start. A user-setfsGroupis preserved.get/list/watchonsecretsandconfigmapsfrom the ConsensusCapsule Role. Nothing in the node pod reads them through the API. Keys and config arrive through volumes, and the UC's RBAC probe only checks the operator's config resources. Existing Roles are updated in place on the next reconcile.EnvoyProxy.spec.imageandHAProxyCapsule.spec.imagenow require a tag or@sha256:digest and rejectlatest, enforced by CEL rules plusmaxLength: 512.ImageRegistrySpec.imagepattern on the NetworkUpgrade* CRDs now requires a tag or digest; a bare repository is rejected.requireDigestOnDeploynow also applies to EnvoyProxy and HAProxyCapsule. An image without a digest fails the reconcile with a terminalImageDigestRequirederror and is not requeued.beacon file uploadwithout--expect-hashor--expect-hash-filenow logs anUnverifiedPackagewarning with the package's SHA-384, asking the operator to confirm it against the release beforefreeze prepare.spec.secrets.hostPathandspec.configFoldermounts are now read-only. Both fields are documented as legacy (prefersecretResourcesand the config CR refs), and each reconcile logs aHostPathVolumewarning when either is used.FROMlines inDockerfile,Dockerfile.beaconandDockerfile.ucare pinned by multi-arch@sha256:digest (debian:bookworm-slim,distroless/static-debian13:nonroot). The weekly grouped Dependabotdockerupdate keeps the digests current.Related Issues