The latest in cloud native technology, served fresh
Keycloak incubating Keycloak is an open-source identity and access management solution for modern applications and services, built on top of industry security standard protocols.
Fix virtual thread check
Virtual threads are enabled by default, but they must not be enabled when CPU count is less than 4
Closes #48792
Signed-off-by: Pedro Ruivo <1492066+pruivo@users.noreply.github.com>
Co-authored-by: Pedro Ruivo <1492066+pruivo@users.noreply.github.com>
Harbor graduated Harbor is an open source registry that secures artifacts with policies and role-based access control, ensures images are scanned and free from vulnerabilities, and signs images as trusted. Can be installed on any Kubernetes environment or on a system with Docker support.
Full Changelog: v2.14.3...v2.14.4-rc1
LoxiLB sandbox eBPF based cloud-native load-balancer. Powering Kubernetes|Edge|5G|IoT|XaaS Apps.
hami sandbox Heterogeneous AI Computing Virtualization Middleware
Full Changelog: v2.8.0...v2.9.0
hami sandbox Heterogeneous AI Computing Virtualization Middleware
Open Cluster Management sandbox changes since v1.2.0
Apply resource in manifestwork ordered by kind (#1500) @qiujian16
split debug controller as standalone service with proper validation (#1461) @haoqing0110
feature: Add new ignore field options in SSA updateStrategy (#1405) @ncr38
Add e2e test for token-based authentication with template addons (#1368) @zhujian7
tls-server-name field of external-managed-kubeconfig is missing (#1502) @rokej
Fix flaky clustermanager integration test (#1493) @qiujian16
Match the exact cluster name for csr renewal (#1476) @qiujian16
fix renew the spoke agent cert request in grpc mode (#1463) @skeeey
Fix Progressing condition stuck at True for overlapping placements (#1456) @zhiweiyin318
fix cma Progressing status addon counting error (#1454) @zhiweiyin318
Fix flaky e2e test: addon CSR cleanup race condition (#1449) @zhujian7
fix: Propagate UserInfo.Extra field in ManifestWork webhook SAR (#1427) @zhujian7
set tokenrequest UID to empty to avoid conflict with the ServiceAccount UID validation (#1423) @zhiweiyin318
Use generate name for manfiestwork generated by manifestworkreplicaset (#1421) @qiujian16
Align PR title verifier prefixes with pull_request_template.md (#1417) @zhiweiyin318
fix: remove flaky time.Sleep from hub timeout controller test (#1388) @zhujian7
fix: handle ComponentNamespace in CI test environment (#1387) @zhujian7
fix: correct variable usage and error messages in ManifestWorkReplicaSet e2e tests (#1386) @zhujian7
replace broken kubebuilder-tools download with setup-envtest (#1383) @haoqing0110
improve event recording logic and test maintainbility (#1376) @haoqing0110
Add KubeStellar Console to ADOPTERS.md (#1484) @clubanderson
docs: add Flower federated learning addon to Ecosystem (#1408) @yanmxa
Bump google.golang.org/grpc from 1.80.0 to 1.81.0 (#1516) @dependabot[bot]
Register hub as local-cluster in local dev setup (#1515) @kahirokunn
update olm manifests (#1514) @zhiweiyin318
Move addon manager's API to v1beta1 (#1511) @qiujian16
Bump the github-actions group with 2 updates (#1508) @dependabot[bot]
Bump github.com/onsi/ginkgo/v2 from 2.28.1 to 2.28.2 (#1503) @dependabot[bot]
Bump open-cluster-management.io/api from 1.2.1-0.20260420020752-a40dfdc05b05 to 1.3.0 in the open-cluster-management-io group (#1501) @dependabot[bot]
chore: Bump open-cluster-management.io/api to pick up the omitzero tag on ClusterDecision.Score in PlacementDecision (#1492) @mikeshng
Bump the github-actions group with 2 updates (#1490) @dependabot[bot]
Bump the k8s-io group with 8 updates (#1489) @dependabot[bot]
Bump the github-actions group with 4 updates (#1488) @dependabot[bot]
Bump helm.sh/helm/v3 from 3.20.1 to 3.20.2 (#1487) @dependabot[bot]
Bump github.com/google/cel-go from 0.27.0 to 0.28.0 (#1483) @dependabot[bot]
Bump github.com/aws/aws-sdk-go-v2/service/eks from 1.81.2 to 1.82.0 in the aws group across 1 directory (#1482) @dependabot[bot]
Bump sigs.k8s.io/cluster-inventory-api from 0.0.0-20251124125836-445319b6307a to 0.1.0 in the k8s-io group (#1481) @dependabot[bot]
Copy TLS ConfigMap to addon namespaces in klusterlet operator (#1480) @zhujian7
Bump step-security/harden-runner from 2.16.0 to 2.16.1 in the github-actions group (#1475) @dependabot[bot]
Bump the aws group with 2 updates (#1474) @dependabot[bot]
refactor cluster kubeapiserver health check with failure threshold (#1473) @zhiweiyin318
Bump github.com/itchyny/gojq from 0.12.18 to 0.12.19 (#1472) @dependabot[bot]
Add TLS profile compliance for gRPC server (#1471) @zhujian7
Bump google.golang.org/grpc from 1.79.3 to 1.80.0 (#1470) @dependabot[bot]
Bump the github-actions group with 3 updates (#1466) @dependabot[bot]
Bump the aws group with 4 updates (#1464) @dependabot[bot]
Enable e2e testing on macOS with docker/podman (#1458) @qiujian16
Bump github/codeql-action from 4.33.0 to 4.34.1 in the github-actions group (#1457) @dependabot[bot]
Bump the k8s-io group with 8 updates (#1455) @dependabot[bot]
Add TLS ConfigMap watch and restart for cluster-manager operator (#1452) @zhujian7
Bump google.golang.org/grpc from 1.79.2 to 1.79.3 (#1451) @dependabot[bot]
Remove unsupported addon webhook hosted mode config (#1450) @bhperry
Bump the aws group with 4 updates (#1441) @dependabot[bot]
Bump the github-actions group with 2 updates (#1440) @dependabot[bot]
Move addon api to beta in registration (#1438) @qiujian16
Bump helm.sh/helm/v3 from 3.19.5 to 3.20.1 (#1433) @dependabot[bot]
Bump github.com/aws/aws-sdk-go-v2/service/eks from 1.80.2 to 1.81.0 in the aws group (#1432) @dependabot[bot]
Bump github.com/aws/aws-sdk-go-v2/service/iam from 1.53.4 to 1.53.5 in the aws group (#1424) @dependabot[bot]
Bump the github-actions group with 3 updates (#1419) @dependabot[bot]
Bump the k8s-io group across 1 directory with 3 updates (#1418) @dependabot[bot]
Replace deprecated kubebuilder-release-tools PR verifier with inline scripts (#1416) @zhiweiyin318
Bump google.golang.org/grpc from 1.79.1 to 1.79.2 (#1415) @dependabot[bot]
Bump kubernetes lib to 1.35 (#1414) @qiujian16
Bump the aws group across 1 directory with 5 updates (#1411) @dependabot[bot]
support install hosted addon via installStrategy (#1410) @zhiweiyin318
Replace legacy envtest setup with sdk-go shared script (#1409) @xuezhaojun
Bump the github-actions group with 5 updates (#1407) @dependabot[bot]
Adopt shared golangci-lint scripts from sdk-go (#1401) @xuezhaojun
Bump the aws group with 5 updates (#1399) @dependabot[bot]
Bump the github-actions group across 1 directory with 2 updates (#1395) @dependabot[bot]
Bump google.golang.org/grpc from 1.78.0 to 1.79.1 (#1392) @dependabot[bot]
Change image tag validation to fail only for tag format mismatches (#1385) @zhujian7
Bump github.com/aws/aws-sdk-go-v2/service/eks from 1.78.0 to 1.79.0 in the aws group (#1382) @dependabot[bot]
Bump github.com/aws/aws-sdk-go-v2/service/eks from 1.77.1 to 1.78.0 in the aws group (#1379) @dependabot[bot]
Bump the github-actions group with 2 updates (#1377) @dependabot[bot]
Bump github.com/aws/aws-sdk-go-v2/service/eks from 1.77.0 to 1.77.1 in the aws group (#1374) @dependabot[bot]
Bump github.com/onsi/gomega from 1.39.0 to 1.39.1 (#1372) @dependabot[bot]
Bump github/codeql-action from 4.31.11 to 4.32.0 in the github-actions group (#1370) @dependabot[bot]
Bump github.com/onsi/ginkgo/v2 from 2.27.5 to 2.28.1 (#1369) @dependabot[bot]
Bump github.com/google/cel-go from 0.26.1 to 0.27.0 (#1366) @dependabot[bot]
Thanks to all our contributors!*
Full Changelog: v1.2.0...v1.3.0
Volcano incubating Important:
This release addresses a security vulnerability and multiple bug fixes. We strongly advise all users to upgrade immediately to protect your systems and data.
A security vulnerability has been discovered in the Volcano webhook server that could allow a pod with network access to the webhook endpoint to cause a denial of service by sending an arbitrarily large HTTP request body, leading to the webhook server being killed by OOM.
Affected Versions:
Fixed Versions:
This vulnerability was reported by @bugbunny-research and mitigated by @JesseStutler.
CVSS Rating: Moderate (6.8) CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
Full Changelog: v1.12.3...v1.12.4
Volcano incubating Important:
This release addresses a security vulnerability and multiple bug fixes. We strongly advise all users to upgrade immediately to protect your systems and data.
A security vulnerability has been discovered in the Volcano webhook server that could allow a pod with network access to the webhook endpoint to cause a denial of service by sending an arbitrarily large HTTP request body, leading to the webhook server being killed by OOM.
Affected Versions:
Fixed Versions:
This vulnerability was reported by @bugbunny-research and mitigated by @JesseStutler.
CVSS Rating: Moderate (6.8) CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
Full Changelog: v1.13.2...v1.13.3
Volcano incubating Important:
This release addresses a security vulnerability and multiple bug fixes. We strongly advise all users to upgrade immediately to protect your systems and data.
A security vulnerability has been discovered in the Volcano webhook server that could allow a pod with network access to the webhook endpoint to cause a denial of service by sending an arbitrarily large HTTP request body, leading to the webhook server being killed by OOM.
Affected Versions:
Fixed Versions:
This vulnerability was reported by @bugbunny-research and mitigated by @JesseStutler.
CVSS Rating: Moderate (6.8) CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
highestTierName in partitionPolicy or subGroupPolicy fails to restrict scheduling to specified HyperNode tiers (#5203 @Tau721)Full Changelog: v1.14.1...v1.14.2
Dapr graduated The Distributed Application Runtime (Dapr) provides APIs that simplify microservice architecture development and increases developer productivity. Whether your communication pattern is service-to-service invocation or pub/sub messaging, Dapr helps you write resilient and secured microservices....
This is the release candidate 1.17.7-rc.1
This update contains the following bug fixes:
When the proto-encoded WorkItem that the orchestrator sends to a connected SDK worker on the GetWorkItems gRPC stream grew larger than the dapr API gRPC server's MaxSendMsgSize (which is the same as --max-body-size, default 4 MiB), the underlying stream.Send returned ResourceExhausted and the entire stream was cancelled.
Every other workflow that happened to be pending on the same stream was cancelled along with it, and the SDK reconnected only to repeat the same failure on the same offending workflow.
Any long-running workflow whose accumulated history (PastEvents + NewEvents + propagated history) crossed the configured --max-body-size could trigger a stream tear-down loop.
Visible symptoms included:
PropagatedHistory could exhibit the same tear-down on the activity work-item path.Neither the orchestrator nor the durabletask gRPC executor measured the size of the WorkItem proto before pushing it onto the stream.
Once the message reached stream.Send, gRPC enforced MaxSendMsgSize and aborted the entire GetWorkItems server stream with ResourceExhausted.
Because the failure was at the transport layer, the runtime had no place to record a structured signal back to the user, and there was no terminal state for an orchestration that could not legally be dispatched.
The orchestrator now precomputes the proto size of the WorkItem it is about to dispatch and compares it to a 95% safety threshold of --max-body-size (the headroom covers the engine's WorkflowStarted event injection plus gRPC framing overhead).
If the threshold would be crossed:
runWorkflow short-circuits before the work item is handed to the durabletask scheduler.callActivity short-circuits before the activity actor is invoked, and the parent workflow is stalled.Either path appends an ExecutionStalled event to the workflow's history with the new StalledReason value PAYLOAD_SIZE_EXCEEDED and transitions the workflow into the existing STALLED state.
The orchestrator's stallable lock is held until the actor is deactivated, so the next activation re-evaluates: if the operator has purged or terminated the workflow, or restarted daprd with a larger --max-body-size, the workflow resumes; otherwise it re-stalls without disturbing other instances on the stream.
When a scheduler pod is killed during workflow execution under load, some workflows become orphaned: they remain in RUNNING state with no further execution, or they reach a terminal state but are never purged despite a configured retention policy.
dapr workflow history shows nothing abnormal, execution simply stops.
dapr workflow list reports the affected completed workflows as much older than the configured retention window.
Any deployment running workflows with a multi-replica scheduler is affected when scheduler pods restart during load.
This is most visible during routine operations such as Kubernetes rolling updates, node drains, or OOM-driven scheduler restarts.
The actor state-store transaction that persists workflow state was not coordinated with the gRPC call that registers the corresponding wake-up reminder in the scheduler service.
These are two independent operations against two different systems with no atomic boundary between them.
When a scheduler pod was killed mid-RPC, the state save had typically completed and the reminder Create was lost.
The reminder failure policy retries an already-persisted reminder forever; it cannot recover a reminder whose Create RPC never reached durable storage.
For completed workflows, the retention path was particularly fragile: the workflow's firing reminder was deleted before the retention reminder was created.
If the retention Create then failed, no reminder remained to drive a retry, leaving the workflow terminal-but-not-purged.
Three changes close the loss windows:
In-process retry on reminder creation.
Every reminder Create now retries with bounded exponential backoff (up to 60 seconds total) before returning to the caller.
Retries reuse the same reminder Name; the scheduler's overwrite-by-name semantics keep them idempotent.
A typical scheduler-pod failover completes in seconds, so the retry transparently heals the failure without surfacing it to the workflow.
Retention reminder created before deletion.
In the completion path, the retention reminder is now registered before the workflow's own reminders are deleted.
If the retention Create still fails after the in-process retry, the firing reminder remains alive and its failure-policy retry brings execution back to the completion path.
Idempotent retention recovery on re-fire.
When a reminder fires for a workflow whose state is already terminal but whose inbox is empty, the runtime now re-issues the retention reminder Create.
The retention reminder name is deterministic, so this is a safe overwrite rather than a duplicate.
This recovers workflows whose completion was persisted in a prior run but whose retention reminder Create was lost.
The retention reminder's due time is now anchored to the workflow's actual completion time rather than the moment of the Create call, so retries converge on a single reminder at a stable due time instead of pushing retention back on every retry.
When the workflow actor on one pod was cancelled mid-flight (typically during a rolling deployment) after dispatching an activity but before its state save committed, the activity actor still completed normally and posted its TaskCompleted event back to the workflow actor's inbox.
On the next workflow activation, the orchestrator re-yielded the same ScheduleTask because its replay state did not yet reflect the dispatch, so the activity actor ran a second time and posted a second TaskCompleted for the same taskScheduledId.
The same shape applied to TaskFailed, TimerFired, and child-workflow completions delivered through the inbox.
The language SDK's process_event handlers for these event kinds silently return when no matching pending task is found, producing zero new actions, so dapr re-fired the wake-up reminder against the same un-cleared inbox and the cycle repeated.
Any deployment running workflows whose hosting pods are restarted during load is affected.
This is most visible during routine operations such as Kubernetes rolling updates or node drains.
Visible symptoms include:
RUNNING while its persisted history grows steadily with full activity payloads.dropping duplicate event: executionStarted warnings on the dapr side, paired with thousands of Ignoring unexpected taskCompleted event with ID = N warnings on the SDK side for the same instance.Two layers were missing safeguards.
First, the workflow actor's addWorkflowEvent (the inbox-write boundary called by the activity actor and by sub-workflow completion delivery) did not deduplicate task-resolution events.
A redelivered completion was appended to the inbox, persisted, and a new wake-up reminder was created, even when the same resolution was already committed to history or queued in the inbox from an earlier delivery.
Second, the orchestrator's callActivities did not check whether the activity it was about to dispatch had already resolved.
When the orchestrator re-yielded a ScheduleTask because its replay state was missing the corresponding TaskScheduled (e.g. after a partial save was lost on cancellation), the activity actor was invoked again, ran the activity body again, and posted yet another TaskCompleted to the inbox.
The two layers compounded: the inbox grew because the dispatch produced new completions, the orchestrator re-ran because the inbox grew, and the SDK silently spun on the unmatched events.
Two complementary checks were added in the workflow actor, both backed by a shared dedup helper:
Inbox-write dedup in addWorkflowEvent.
A TaskCompleted / TaskFailed / TimerFired / ChildWorkflowInstance{Completed,Failed} whose correlator (taskScheduledId or timerId) already appears in either state.History or state.Inbox is dropped before it reaches state.AddToInbox, the transactional save, and the new-event reminder.
EventRaised and ExecutionTerminated are intentionally excluded: EventRaised is a user signal that may legitimately repeat, and ExecutionTerminated is idempotent.
Dispatch-skip in callActivities.
Before invoking the activity actor for a TaskScheduled, the workflow actor checks whether a matching TaskCompleted or TaskFailed for the same taskScheduledId is already in state.History or state.Inbox.
If it is, the dispatch is suppressed; the orchestrator's stale re-yield no longer triggers a second activity run.
The underlying engine in durabletask-go was hardened in lockstep: runtimestate.AddEvent now also rejects a resolution event whose correlator is already present, providing defence in depth for any caller that bypasses the actor's inbox-write path.
The Stalled-clear logic runs only on a successful add, so a duplicate-rejection error preserves a prior stalled state.
After upgrading, persisted histories from older daprd versions that already accumulated duplicates are silently truncated on next workflow load (the duplicate entries are not re-added to the in-memory OldEvents), so the upgrade is one-way for that state.
Operators who downgraded a control plane from 1.18 back to 1.17 saw dapr-sentry crash on startup with:
fatal: error creating CA: failed to get CA bundle: failed to verify CA bundle: unsupported key type ed25519.PrivateKey
The same failure mode also rejected RSA-keyed issuer bundles. The crash is hit before sentry serves any traffic, so every sidecar that depends on sentry for its identity certificate stops being able to obtain or rotate one.
Any 1.17 control plane whose dapr-trust-bundle secret was generated by, or migrated through, a newer Dapr release that issues Ed25519 (or RSA) issuer keys is affected. In practice this includes:
Sentry crash-loops, no new mTLS identities are issued, and existing certificates are not rotated. Sidecars whose certs have not yet expired keep working; sidecars that come up fresh, restart, or hit cert expiry start failing to obtain identities.
dapr/kit's crypto/pem.EncodePrivateKey (used by sentry to re-encode the issuer key it just decoded from the trust bundle) only matched *ecdsa.PrivateKey and *ed25519.PrivateKey in its type switch. ed25519.PrivateKey is itself a []byte alias rather than a struct, so the *ed25519.PrivateKey case never matched a real Ed25519 key. RSA private keys were never listed at all.
When sentry called EncodePrivateKey on an Ed25519 or RSA issuer key it fell through to the default branch and returned unsupported key type %T, which the CA initialiser surfaced as a fatal error.
dapr/kit's EncodePrivateKey now matches ed25519.PrivateKey (value form) and *rsa.PrivateKey alongside *ecdsa.PrivateKey. All three round-trip through PKCS#8 unchanged. Dapr 1.17.7 picks up this fix by bumping github.com/dapr/kit to v0.17.1, which also includes table-driven roundtrip tests for ECDSA P-256, RSA-2048, and Ed25519 to guard the regression.
No operator action is required beyond upgrading sentry to 1.17.7. Existing trust bundles are read as-is; the issuer key is not regenerated.
When a sidecar received SIGTERM, Kafka pub/sub subscriptions tore down their consumer group session before the messages already fetched from the broker had been delivered to the application.
The contrib retry loop observed context canceled, the runtime logged Too many failed attempts at processing Kafka message ... Error: context canceled, and the broker handed the same offsets to whichever consumer won the rebalance.
Any deployment running Kafka pub/sub through a multi-replica subscriber was affected on rolling restarts, node drains, or any other graceful-shutdown event.
Visible symptoms included:
Too many failed attempts at processing Kafka message and kafka: tried to use a consumer group that was closed errors during shutdown.The runtime's Subscription.Stop() set its closed flag immediately on entry, which caused the handler closure to reject any further deliveries from contrib with errors.New("subscription is closed").
Contrib treated that as an error and retried inside an already-closing session, eventually giving up and surrendering the partition to the rebalance.
The "in-flight" definition was also too narrow: only handlers already inside the closure counted, while messages that contrib had pulled from the broker but not yet handed to the handler were considered absent and got the rejection path.
A new pubsub.PausableSubscriber capability lets the runtime ask a component to stop fetching from the broker without tearing down the consumer group session.
On graceful shutdown the runtime now:
PauseAll, which stops broker fetches while keeping the session and partition assignments alive).closed=false during a bounded drain window so handlers continue delivering buffered messages to the application via postman.inflight counter with a stable-quiet predicate (100 ms of consecutive zero readings on the paused path) so the drain does not seal in the sub-millisecond gap between handler return and the next claim-buffer read.StopAllSubscriptionsForever and prevent the block-shutdown timer from starting.The components-contrib Kafka component additionally gates consumerGroup.Close() on the last subscription exiting (so multi-topic pubsubs no longer race a sibling subscription's reload into a closed group) and demotes the Too many failed attempts log to debug when the cause is shutdown rather than real retry exhaustion.
When a Kafka bulk subscriber's buffer filled to maxMessagesCount and was flushed before its maxAwaitDurationMs window had elapsed, the await ticker continued firing on its original schedule.
Any subsequent partial batch was then flushed within (often well under) one period of the count-based flush instead of waiting for a fresh maxAwaitDurationMs window from the moment the buffer was last drained.
Any deployment using Kafka bulk pub/sub subscriptions with both maxMessagesCount and maxAwaitDurationMs configured was affected.
Visible symptoms included:
maxAwaitDurationMs after a count-based flush.In ConsumeClaim, the bulk path used a single time.Ticker constructed from maxAwaitDurationMs to trigger time-based flushes.
When the count threshold (len(messages) >= maxMessagesCount) was reached and flushBulkMessages was called, the ticker was not reset.
The next tick still fired at its original wall-clock schedule, so a partial batch arriving just after a count-flush was eligible for flush after only the residual portion of the original ticker period rather than a full maxAwaitDurationMs.
After a count-based flush in ConsumeClaim, the await ticker is now reset to a fresh maxAwaitDurationMs window via ticker.Reset, anchoring the next time-based flush to the moment of the count-flush.
Go 1.23+ guarantees that Ticker.Reset discards any tick that was queued before the call, so no stale tick can fire immediately after the reset and short-circuit the new window.
Partial batches now consistently wait a full maxAwaitDurationMs after the most recent flush, regardless of whether that flush was triggered by the count threshold or the timer.
Meshery sandbox As a self-service engineering platform, Meshery enables collaborative design and operation of cloud and cloud native infrastructure.
Thank you to our contributors for making this release possible:
@Copilot, @Joyboy48, @Junnygram, @Maanvi212006, @Mooosiee, @PragalvaXFREZ, @YASHMAHAKAL, @alexquincy, @aprv10, @chaitanyamedidar, @fitzergerald, @hebypaul, @hortison, @jahnavigajjala-3, @l5io, @leecalcote, @marryamabid, @meshery-ci, @miacycle, @pontusringblom, @rishiraj38, @ritzorama, @suzy-g38, @winkletinkle and @yi-nuo426
SOPS sandbox sops is an editor of encrypted files that supports YAML, JSON, ENV, INI and BINARY formats and encrypts with AWS KMS, GCP KMS, Azure Key Vault, age, and PGP.
To install sops, download one of the pre-built binaries provided for your platform from the artifacts attached to this release.
For instance, if you are using Linux on an AMD64 architecture:
mv sops-v3.13.0.linux.amd64 /usr/local/bin/sops
chmod +x /usr/local/bin/sops">
# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.13.0/sops-v3.13.0.linux.amd64# Move the binary in to your PATH
mv sops-v3.13.0.linux.amd64 /usr/local/bin/sops# Make the binary executable
chmod +x /usr/local/bin/sops
The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC. To validate the signature of this file, run the following commands:
cosign verify-blob sops-v3.13.0.checksums.txt
--bundle sops-v3.13.0.checksums.sigstore.json
--certificate-identity-regexp=https://github.com/getsops
--certificate-oidc-issuer=https://token.actions.githubusercontent.com">
# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.13.0/sops-v3.13.0.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.13.0/sops-v3.13.0.checksums.sigstore.json# Verify the checksums file
cosign verify-blob sops-v3.13.0.checksums.txt
--bundle sops-v3.13.0.checksums.sigstore.json
--certificate-identity-regexp=https://github.com/getsops
--certificate-oidc-issuer=https://token.actions.githubusercontent.com
To verify the integrity of the downloaded binary, you can utilize the checksums file after having validated its signature:
# Verify the binary using the checksums file
sha256sum -c sops-v3.13.0.checksums.txt --ignore-missingThe SLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an in-toto link metadata file named sops-v3.13.0.intoto.jsonl. To verify the provenance of an artifact, you can utilize the slsa-verifier tool:
slsa-verifier verify-artifact <artifact>
--provenance-path sops-v3.13.0.intoto.jsonl
--source-uri github.com/getsops/sops
--source-tag v3.13.0">
# Download the metadata file
curl -LO https://github.com/getsops/sops/releases/download/v3.13.0/sops-v3.13.0.intoto.jsonl# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact>
--provenance-path sops-v3.13.0.intoto.jsonl
--source-uri github.com/getsops/sops
--source-tag v3.13.0
The sops binaries are also available as container images, based on Debian (slim) and Alpine Linux. The Debian-based container images include any dependencies which may be required to make use of certain key services, such as GnuPG, AWS KMS, Azure Key Vault, and Google Cloud KMS. The Alpine-based container images are smaller in size, but do not include these dependencies.
These container images are available for the following architectures: linux/amd64 and linux/arm64.
ghcr.io/getsops/sops:v3.13.0ghcr.io/getsops/sops:v3.13.0-alpinequay.io/getsops/sops:v3.13.0quay.io/getsops/sops:v3.13.0-alpineThe container images are signed using Cosign with GitHub OIDC. To validate the signature of an image, run the following command:
cosign verify ghcr.io/getsops/sops:v3.13.0 \ --certificate-identity-regexp=https://github.com/getsops \ --certificate-oidc-issuer=https://token.actions.githubusercontent.com \ -o text
The container images include SLSA provenance attestations. For more information around the verification of this, please refer to the slsa-verifier documentation.
The Software Bill of Materials (SBOM) for each binary is accessible within the artifacts enclosed with this release. It is presented as an SPDX JSON file, formatted as <binary>.spdx.sbom.json.
--filename by @felixfontein in #2155--indent global flag value and pass it to store configs by @skirino in #2156Full Changelog: v3.12.2...v3.13.0
Linkerd graduated Ultra light, ultra simple, ultra powerful. Linkerd adds security, observability, and reliability to Kubernetes, without the complexity.
The minimum supported Kubernetes version for this and future releases is 1.31.
This release significantly reduces the amount of memory used by the destination controller on busy systems. It also allows setting the node port for the health check of a Linkerd multicluster gateway (fixing issue #15172 – thanks, Aldo Fuster Turpin!), cleans up some CI permissions (fixing issue #15182 – thanks, Gagan H R!), and correctly handles mirroring headless Services with the same name in different namespaces (fixing issue #15200 – thanks, Cody Bond!). Finally, it corrects the instructions about how to install the Gateway API CRDs when linkerd install --crds detects that they are missing, and bumps the minimum supported Kubernetes version to 1.31.
Full Changelog: edge-26.4.4...edge-26.5.1
Linkerd graduated Ultra light, ultra simple, ultra powerful. Linkerd adds security, observability, and reliability to Kubernetes, without the complexity.
N/A
This release improves support for newer Gateway API versions by allowing the policy validator to correctly function when new Gateway API resources are created with stanzas it doesn't understand, fixing issue #14986. It also improves the logic around using annotations to name metrics (fixing issue #15175 – thanks, Simon Dickhoven!), and correctly supports linkerd upgrade when using an external CA (fixing issue #15025).
Full Changelog: edge-26.4.3...edge-26.4.4
Kubescape incubating Kubescape is an open source security and compliance platform that scans clusters, Kubernetes manifest files (YAML files, and Helm charts), code repositories, container registries and images. It detects misconfigurations according to frameworks such as the NSA-CISA, MITRE ATT&CK® and CIS, as well as software vulnerabilities, and calculates risk scores.
Released by GoReleaser.
WasmEdge Runtime sandbox WasmEdge provides a high-performance, lightweight, secure, and extensible WebAssembly runtime for cloud-native applications. It is an OCI compliant container that is integrated into Docker, containerd, crun and many Kubernetes projects....
This is the bug fix for the 0.16.x versions.
Fixed issues:
CI:
Thank all the contributors who made this release possible!
harukiki97, hydai, Yi-Ying He
If you want to build from source, please use WasmEdge-0.16.3-src.tar.gz instead of the zip or tarball provided by GitHub directly.
KubeStellar sandbox 
CloudNativePG sandbox CloudNativePG is a comprehensive platform designed to seamlessly manage PostgreSQL databases within Kubernetes environments, covering the entire operational lifecycle from initial deployment to ongoing maintenance
Release date: May 8, 2026
CVE-2026-44477 / GHSA-423p-g724-fr39: metrics exporter privilege escalation: the metrics exporter no longer authenticates as the postgres superuser. It now uses a dedicated cnpg_metrics_exporter role with pg_monitor privileges only, closing a chain that let a low-privilege database user gain PostgreSQL superuser. (GHSA-423p-g724-fr39)
Upgrade impact: custom monitoring queries that read user-owned tables, or use target_databases: '*' against databases where PUBLIC CONNECT has been revoked, need explicit GRANT statements to cnpg_metrics_exporter. See "Custom query privileges and safety" and "Manually creating the metrics exporter role" in the monitoring documentation.
For replica clusters, upgrade the source primary cluster before any replica clusters that consume from it. The cnpg_metrics_exporter role is created on the source primary and replicates downstream; a replica cluster upgraded first will scrape against a missing role until the source primary upgrades. The manual-recovery section linked above also covers replica clusters.
Schema-qualified catalog references in default monitoring queries: hardened the shipped monitoring configuration and documentation samples by qualifying every pg_catalog object explicitly. Unqualified references resolve through search_path, which a database user can manipulate to shadow built-in objects. (#10576)
Discoverable SBOM and provenance attestations: SBOM and SLSA provenance attached to operator container images now follow the OCI 1.1 Referrers spec, so standard registry tooling and supply-chain scanners can discover them automatically. (#10601)
CVE remediation in github.com/jackc/pgx/v5: bumped to v5.9.2 to pick up upstream fixes for CVE-2026-33816 (memory-safety in pgproto3) and GHSA-j88v-2chj-qfwx (SQL injection via simple-protocol dollar-quoted string handling). (#10437, #10499)
CVE remediation in the Go runtime: built with Go 1.26.3 to pick up upstream fixes in crypto/x509, crypto/tls, net/http, and net (CVE-2026-32280, CVE-2026-32281, CVE-2026-33810, CVE-2026-33814, CVE-2026-33811, CVE-2026-39825). (#10463, #10647)
Build pipeline hardening: the Go 1.26.3 bump also addresses CVE-2026-42501 (cmd/go module-checksum validation), reducing supply-chain exposure during release builds. The affected code paths are not reachable from the running operator. (#10647)
VerifyPeerCertificate to VerifyConnection, which runs on every completed handshake (the former is skipped on resumed TLS 1.3 sessions). Session resumption is not enabled in CloudNativePG today, so this has no observable effect, but it future-proofs verification if session caching is introduced later. (#10478) Fixed a failover window where the former primary kept its primary label. If it returned during failover (for example, after a transient network partition), the -rw service kept routing to it, replicas could reconnect, and committed writes were lost to pg_rewind. The old primary is now labeled unhealthy to isolate it from service traffic during failover. (#10409)
Fixed failover not being triggered when the node hosting the primary becomes unreachable. The operator now reads the pod's Ready condition (flipped to False by the node controller when the kubelet stops reporting) instead of ContainersReady, which stays stale as True in that scenario. Combined with the spurious-failover guard (#10445), failover triggers only when Kubernetes itself marks the pod not Ready. (#10448)
Fixed spurious failovers caused by transient failures on the primary's HTTP status endpoint. (#10445)
Fixed escaping of backslashes and control characters in PostgreSQL configuration values. Previously, such characters in parameters like log_line_prefix could corrupt the configuration file or be silently stripped at runtime. (#10515)
Fixed restore_command construction to shell-quote each argument. Values such as a destinationPath containing whitespace (for example, s3://my bucket/wal) were word-split by the POSIX shell and passed to the WAL restore tool as separate arguments. (#10518)
Tightened recoveryTarget validation in the admission webhook: targetXID must now be a non-negative 32-bit integer, and targetName must be shorter than 64 bytes and free of ASCII control characters. Malformed values are rejected at admission instead of failing later during PostgreSQL recovery. (#10565)
Fixed snapshot restores failing when leftover pgsql_tmp* directories were present in the data directory. (#10447)
Fixed a deadlock occurring when PVC storage size and resource requests are changed simultaneously. (#10427)
CloudNativePG sandbox CloudNativePG is a comprehensive platform designed to seamlessly manage PostgreSQL databases within Kubernetes environments, covering the entire operational lifecycle from initial deployment to ongoing maintenance
Release date: May 8, 2026
CVE-2026-44477 / GHSA-423p-g724-fr39: metrics exporter privilege escalation: the metrics exporter no longer authenticates as the postgres superuser. It now uses a dedicated cnpg_metrics_exporter role with pg_monitor privileges only, closing a chain that let a low-privilege database user gain PostgreSQL superuser. (GHSA-423p-g724-fr39)
Upgrade impact: custom monitoring queries that read user-owned tables, or use target_databases: '*' against databases where PUBLIC CONNECT has been revoked, need explicit GRANT statements to cnpg_metrics_exporter. See "Custom query privileges and safety" and "Manually creating the metrics exporter role" in the monitoring documentation.
For replica clusters, upgrade the source primary cluster before any replica clusters that consume from it. The cnpg_metrics_exporter role is created on the source primary and replicates downstream; a replica cluster upgraded first will scrape against a missing role until the source primary upgrades. The manual-recovery section linked above also covers replica clusters.
Schema-qualified catalog references in default monitoring queries: hardened the shipped monitoring configuration and documentation samples by qualifying every pg_catalog object explicitly. Unqualified references resolve through search_path, which a database user can manipulate to shadow built-in objects. (#10576)
Discoverable SBOM and provenance attestations: SBOM and SLSA provenance attached to operator container images now follow the OCI 1.1 Referrers spec, so standard registry tooling and supply-chain scanners can discover them automatically. (#10601)
CVE remediation in github.com/jackc/pgx/v5: bumped to v5.9.2 to pick up upstream fixes for CVE-2026-33816 (memory-safety in pgproto3) and GHSA-j88v-2chj-qfwx (SQL injection via simple-protocol dollar-quoted string handling). (#10436, #10498)
CVE remediation in the Go runtime: built with Go 1.26.3 to pick up upstream fixes in crypto/x509, crypto/tls, net/http, and net (CVE-2026-32280, CVE-2026-32281, CVE-2026-33810, CVE-2026-33814, CVE-2026-33811, CVE-2026-39825). (#10462, #10647)
Build pipeline hardening: the Go 1.26.3 bump also addresses CVE-2026-42501 (cmd/go module-checksum validation), reducing supply-chain exposure during release builds. The affected code paths are not reachable from the running operator. (#10647)
VerifyPeerCertificate to VerifyConnection, which runs on every completed handshake (the former is skipped on resumed TLS 1.3 sessions). Session resumption is not enabled in CloudNativePG today, so this has no observable effect, but it future-proofs verification if session caching is introduced later. (#10478) Fixed a failover window where the former primary kept its primary label. If it returned during failover (for example, after a transient network partition), the -rw service kept routing to it, replicas could reconnect, and committed writes were lost to pg_rewind. The old primary is now labeled unhealthy to isolate it from service traffic during failover. (#10409)
Fixed failover not being triggered when the node hosting the primary becomes unreachable. The operator now reads the pod's Ready condition (flipped to False by the node controller when the kubelet stops reporting) instead of ContainersReady, which stays stale as True in that scenario. Combined with the spurious-failover guard (#10445), failover triggers only when Kubernetes itself marks the pod not Ready. (#10448)
Fixed spurious failovers caused by transient failures on the primary's HTTP status endpoint. (#10445)
Fixed escaping of backslashes and control characters in PostgreSQL configuration values. Previously, such characters in parameters like log_line_prefix could corrupt the configuration file or be silently stripped at runtime. (#10515)
Fixed restore_command construction to shell-quote each argument. Values such as a destinationPath containing whitespace (for example, s3://my bucket/wal) were word-split by the POSIX shell and passed to the WAL restore tool as separate arguments. (#10518)
Tightened recoveryTarget validation in the admission webhook: targetXID must now be a non-negative 32-bit integer, and targetName must be shorter than 64 bytes and free of ASCII control characters. Malformed values are rejected at admission instead of failing later during PostgreSQL recovery. (#10565)
Fixed snapshot restores failing when leftover pgsql_tmp* directories were present in the data directory. (#10447)
Fixed a deadlock occurring when PVC storage size and resource requests are changed simultaneously. (#10427)
BFE sandbox Open-source layer 7 load balancer derived from proprietary Baidu FrontEnd
Kubescape incubating Kubescape is an open source security and compliance platform that scans clusters, Kubernetes manifest files (YAML files, and Helm charts), code repositories, container registries and images. It detects misconfigurations according to frameworks such as the NSA-CISA, MITRE ATT&CK® and CIS, as well as software vulnerabilities, and calculates risk scores.
Released by GoReleaser.
TiKV graduated A distributed transactional key-value database. Based on the design of Google Spanner and HBase, but simpler to manage and without dependencies on any distributed filesystem
ref #15990\n\nbump tikv pkg version to 8.5.6 for feature/fts\n\nSigned-off-by: okjiang 819421878@qq.com\nSigned-off-by: timzxz xiaozhou.zhu@pingcap.com\n\nCo-authored-by: okJiang 819421878@qq.com\nCo-authored-by: timzxz xiaozhou.zhu@pingcap.com
metal3-io incubating Provision bare metal hardware via k8s-native APIs, including integration with the Cluster API.
context to PreprovisioningImageFormats func (#3165)force_persistent_boot_device: <value> for deploy_interface: direct (#2614)The image for this release is: v0.13.0
Thanks to all our contributors! 😊
WasmEdge Runtime sandbox WasmEdge provides a high-performance, lightweight, secure, and extensible WebAssembly runtime for cloud-native applications. It is an OCI compliant container that is integrated into Docker, containerd, crun and many Kubernetes projects....
This is the hot fix for 0.16.x versions.
Fixed issues:
Tests:
CI:
Thank all the contributors who made this release possible!
Divyansh Khatri, Karan Lokchandani, Meet Jain, SANCHIT KUMAR, SriramB, Vishal Malyan, Wang-Yang Li, Yi-Ying He, hydai, piyush kumar
If you want to build from source, please use WasmEdge-0.16.2-alpha.1-src.tar.gz instead of the zip or tarball provided by GitHub directly.
Kubean sandbox Product ready cluster lifecycle management toolchains based on kubespray and other cluster LCM engine.
Full Changelog: v0.34.1...v0.34.2
| Default Kubernetes Version | Supported Kubernetes Version Range |
|---|---|
| 1.34.7 | '1.35.4' '1.35.3' '1.35.2' '1.35.1' '1.35.0' '1.34.7' '1.34.6' '1.34.5' '1.34.4' '1.34.3' '1.34.2' '1.34.1' '1.34.0' '1.33.11' '1.33.10' '1.33.9' '1.33.8' '1.33.7' '1.33.6' '1.33.5' '1.33.4' '1.33.3' '1.33.2' '1.33.1' '1.33.0' |
KubeArmor sandbox Runtime protection for Kubernetes & other cloud Workloads. Kubearmor provides a observability and policy enforcement system to restrict any unwanted, malicious behaviour of cloud-native workloads at runtime.
Volcano incubating Release Volcano v1.15.0-alpha.0 version
Kgateway sandbox An Envoy-powered, Kubernetes-native API Gateway that integrates Kubernetes Gateway API with a control plane for API connectivity in any cloud environment.
http2ProtocolOptions support to ListenerPolicy and HTTPListenerPolicy for configuring downstream HTTP/2 settings on Envoy listeners. (#13991)http2ProtocolOptions support to ListenerPolicy and HTTPListenerPolicy for configuring downstream HTTP/2 settings on Envoy listeners. Added downstream TCP keepalive configuration to ListenerPolicy. (#13995)Thanks to all the contributors who made this release possible:
The kgateway project is available as a Helm chart and docker images.
The Helm charts are available at:
The docker images are available at:
Try installing this release:
helm install kgateway-crds oci://cr.kgateway.dev/kgateway-dev/charts/kgateway-crds --version v2.3.0-rc.2 --namespace kgateway-system --create-namespace
helm install kgateway oci://cr.kgateway.dev/kgateway-dev/charts/kgateway --version v2.3.0-rc.2 --namespace kgateway-system --create-namespace
For detailed installation instructions and next steps, please visit our quickstart guide.
k3s sandbox Lightweight Kubernetes
This release updates Kubernetes to v1.36.0, and fixes a number of issues.
For more details on what's new, see the Kubernetes release notes.
imports pointing at versioned drop-in directories: config.toml.d for v2 config and config-v3.toml.d for v3 (e.g. /var/lib/rancher/k3s/agent/etc/containerd/config.toml.d/*.toml and .../config-v3.toml.d/*.toml). Additional .toml files in the matching directory are automatically loaded by containerd. Use these directories for drop-in config (e.g. proxy plugins, custom runtimes, or debug settings) without modifying the main config or custom templates.| Component | Version |
|---|---|
| Kubernetes | v1.36.0 |
| Kine | v0.14.16 |
| SQLite | 3.51.3 |
| Etcd | v3.6.7-k3s1 |
| Containerd | v2.2.3-k3s1 |
| Runc | v1.4.2 |
| Flannel | v0.28.4 |
| Metrics-server | v0.8.1 |
| Traefik | v3.6.13 |
| CoreDNS | v1.14.2 |
| Helm-controller | v0.17.1 |
| Local-path-provisioner | v0.0.35 |
As always, we welcome and appreciate feedback from our community of users. Please feel free to:
Podman Container Tools sandbox A set of tools providing full management of container lifecycle, including Podman, Buildah, and Skopeo, which manage containers and images without requiring a daemon or root privileges.
podman machine init --image command when run on Windows using the Hyper-V backend can run PowerShell-escaped commands from the user-specified image path on in a PowerShell session on the host (GHSA-hc8w-h2mf-hp59).unless-stopped restart policy would not restart after a reboot when podman-restart.service was enabled (#28152).Entrypoint="" in a Quadlet .container file did not clear the container's entrypoint (#28213).HealthCmd in a Quadlet .container file to a command that included double-quotes (") would result in a nonfunctional healthcheck due to a parsing issue (#28409).host network mode (#28289).shell driver due to options from the default driver being improperly added.| j | Next release |
| k | Previous release |
| o or Enter | Open focused release in new tab |
| / or s | Focus search input |
| ? | Show this help |
| t | Toggle dark/light theme |
| Space | Page down |
| Shift + Space | Page up |
| h | Scroll to top |
| Esc | Close help / Blur search / Clear focus |
Tip: Keyboard shortcuts work when you're not typing in an input field.