Redpanda

Developer Tools

A Kafka-compatible streaming platform with no ZooKeeper and no JVM.

Latest v26.1.15 · by Redpanda DataWebsiteredpanda-data/redpanda

Release activity

Release activity — 10 releases across 10 days since May 14, 2026. Each cell is one day; darker means more releases that day. Nothing is recorded before May 14, 2026. Older weeks are hidden at this screen width.
MayJunJulAug
SundayNo releases on May 17, 2026No releases on May 24, 2026No releases on May 31, 2026No releases on Jun 7, 2026No releases on Jun 14, 2026No releases on Jun 21, 20261 release on Jun 28, 2026No releases on Jul 5, 2026No releases on Jul 12, 2026No releases on Jul 19, 2026No releases on Jul 26, 2026No releases on Aug 2, 2026No releases on Aug 9, 2026
MondayNo releases on May 18, 2026No releases on May 25, 2026No releases on Jun 1, 2026No releases on Jun 8, 2026No releases on Jun 15, 2026No releases on Jun 22, 2026No releases on Jun 29, 2026No releases on Jul 6, 2026No releases on Jul 13, 2026No releases on Jul 20, 2026No releases on Jul 27, 2026No releases on Aug 3, 2026No releases on Aug 10, 2026
TuesdayNo releases on May 19, 2026No releases on May 26, 2026No releases on Jun 2, 2026No releases on Jun 9, 2026No releases on Jun 16, 2026No releases on Jun 23, 2026No releases on Jun 30, 2026No releases on Jul 7, 2026No releases on Jul 14, 2026No releases on Jul 21, 20261 release on Jul 28, 2026No releases on Aug 4, 2026No releases on Aug 11, 2026
WednesdayNo releases on May 20, 2026No releases on May 27, 2026No releases on Jun 3, 2026No releases on Jun 10, 2026No releases on Jun 17, 2026No releases on Jun 24, 2026No releases on Jul 1, 2026No releases on Jul 8, 2026No releases on Jul 15, 2026No releases on Jul 22, 2026No releases on Jul 29, 2026No releases on Aug 5, 2026
Thursday1 release on May 14, 2026No releases on May 21, 2026No releases on May 28, 20261 release on Jun 4, 2026No releases on Jun 11, 2026No releases on Jun 18, 20261 release on Jun 25, 2026No releases on Jul 2, 2026No releases on Jul 9, 2026No releases on Jul 16, 2026No releases on Jul 23, 2026No releases on Jul 30, 2026No releases on Aug 6, 2026
FridayNo releases on May 15, 20261 release on May 22, 2026No releases on May 29, 2026No releases on Jun 5, 20261 release on Jun 12, 2026No releases on Jun 19, 2026No releases on Jun 26, 2026No releases on Jul 3, 2026No releases on Jul 10, 20261 release on Jul 17, 20261 release on Jul 24, 2026No releases on Jul 31, 20261 release on Aug 7, 2026
SaturdayNo releases on May 16, 2026No releases on May 23, 2026No releases on May 30, 2026No releases on Jun 6, 2026No releases on Jun 13, 2026No releases on Jun 20, 2026No releases on Jun 27, 2026No releases on Jul 4, 2026No releases on Jul 11, 2026No releases on Jul 18, 2026No releases on Jul 25, 2026No releases on Aug 1, 2026No releases on Aug 8, 2026

10 releases since May 14, 2026

Changelog

v26.1.15

Changed 2
  • rpk shadow update in editor mode now replaces the entire Shadow Link configuration instead of merging changed fields, so list-valued fields can shrink or be cleared
  • rpk cluster health will now display any nodes that may be in maintenance mode
Fixed 11
  • Fix the registered config name for leader_balancer_node_mute_timeout
  • Fix a bug in which L0 batches in a cloud topic forgot to preserve last_offset_delta in their header, leading to an under-declared last offset which can stall consumers, skip records, or halt exact-offset replication
  • Fix a bug in which topics with min.compaction.lag.ms left unconfigured with produced batches holding timestamps in the future would be considered ineligible for compaction
  • Fix a bug in which transient TOPIC_AUTHORIZATION_FAILED errors and SASL authentication failures were possible during application of a controller snapshot
  • Fix a bug where corrupted storage would not yield a bad CRC in returned record batches
  • Fix a bug where having a cloud topic read replica on a given cluster would prevent L0 objects on that cluster from being garbage collected
Bug Fixes
  • Fix the registered config name for leader_balancer_node_mute_timeout. by @WillemKauf in #31360
  • Fixes a bug in which L0 batches in a cloud topic forgot to preserve last_offset_delta in their header, leading to an under-declared last offset which can stall consumers, skip records, or halt exact-offset replication. by @WillemKauf in #31363
  • Fixes a bug in which topics with min.compaction.lag.ms left unconfigured with produced batches holding timestamps in the future would be considered ineligible for compaction by @WillemKauf in #31459
  • Fixes a bug in which transient TOPIC_AUTHORIZATION_FAILED errors and SASL authentication failures were possible during application of a controller snapshot. by @WillemKauf in #31437
  • Fixes a bug where corrupted storage would not yield a bad CRC in returned record batches. by @andrwng in #31388
  • Fixes a bug where having a cloud topic read replica on a given cluster would prevent L0 objects on that cluster from being garbage collected. by @andrwng in #31391
  • Updating a Shadow Link that uses PLAIN authentication no longer fails when the password is omitted; the stored password is preserved. by @r-vasquez in #31421
  • #31448 rpk connect install --connect-version no longer rejects versions with a segment of three or more digits, which had blocked pinning any Redpanda Connect release since 4.100.0. Malformed versions with trailing characters are now rejected during validation rather than failing at download. by @prakhargarg105 in #31449
  • rpk security secrets list no longer truncates its output at 100 secrets. by @simon0191 in #31436
  • rpk shadow create no longer fails secret-reference validation on clusters with more than one page of REDPANDA_CLUSTER-scoped secrets. by @simon0191 in #31436
  • rpk shadow update in editor mode now replaces the entire Shadow Link configuration instead of merging changed fields, so list-valued fields (e.g. topic filters) can shrink or be cleared. by @r-vasquez in #31421
Improvements
  • #31335 Fixes an issue where /v1/usage responses could cause oversized allocations for clusters with a large number of Iceberg-enabled topics. by @WillemKauf in #31337
  • rpk cluster health will now display any nodes that may be in maintenance mode. by @alextreichler in #31352

Full Changelog: https://github.com/redpanda-data/redpanda/compare/v26.1.14...v26.1.15

View originalPermalink
How v26.1.15 went

v26.2.1

Added 20
  • Redpanda Enterprise now supports major version rollback via unfinalized upgrades with rpk cluster upgrade finalize and rpk cluster upgrade status commands
  • Shadowing from non-Redpanda Schema Registries using the HTTP Schema Registry API with shadow_schema_registry_api option
  • Schema Registry sync shadow links now enforce max_source_requests_per_second setting and honor Retry-After response headers
  • Schema Registry shadowing exports sync totals as shadow_link_schema_registry_* counters on metrics endpoints
  • Shadow links can mirror RBAC roles from source cluster to destination with configurable sync interval and role-name filters
  • rpk now supports role_sync_options when creating a Shadow Link

Redpanda v26.2 Release Notes

Features
  • Redpanda Enterprise (excludes Redpanda BYOC/Dedicated/Serverless) now supports major version rollback via ‘unfinalized’ upgrades. rpk cluster upgrade finalize and rpk cluster upgrade status manage deferred (unfinalized) major-version upgrades. (#30930)
  • Shadowing from non-Redpanda Schema Registries using the HTTP Schema Registry API. rpk shadow provides support for the new Schema Registry Sync option shadow_schema_registry_api in Shadow Links. (#30860)
  • Schema Registry sync shadow links now enforce the link's max_source_requests_per_second setting (default 30 requests/sec) when reading from the source registry, and honor a throttling source's Retry-After response header. (#31101)
  • Schema Registry shadowing now exports its sync totals as shadow_link_schema_registry_* counters on the internal and public metrics endpoints, labelled by shadow_link_name. (#31067)
  • Shadow links can now mirror RBAC roles from the source cluster to the destination. Configure role sync on the link with a sync interval and role-name filters to select which roles are kept in sync. (#30946)
  • rpk now supports role_sync_options when creating a Shadow Link. (#30909)
  • Shadowing now supports Cloud Topics. (#30073)
  • Tiered Storage V2 beta. A new default_redpanda_storage_mode_tiered_impl cluster config (tiered_v1 | tiered_v2, default tiered_v1) selects whether the tiered value of the redpanda.storage.mode topic property refers to classic Tiered Storage or the new version of tiered storage. Tiered Storage v2 is a beta feature in v26.2. (#30966)
  • New read-only redpanda.storage.mode.impl topic property reports the exact implementation of every topic's storage mode (unset|local|tiered_v1|tiered_v2|cloud), and can be supplied on topic creation to select the storage mode precisely. Topics using the tiered_v2 implementation (beta) can only be created once the whole cluster runs v26.2. (#30966)
  • Schema Registry context support is now enabled by default. Subjects of the form :.context:subject are parsed into a separate context. See the upgrade considerations before upgrading clusters that may have stored literal :.-prefixed subject names. (#30365)
  • Schema Registry now accepts /contexts/{context}/... prefixed URLs on all endpoints, allowing serde clients to target a non-default context by configuring their base URL (e.g. schema.registry.url=http://host:8081/contexts/.myctx). (#30189)
  • Add OAUTHBEARER SASL mechanism support to rpk, enabling OIDC-based authentication for the Kafka client, admin API, and schema registry. Pass the token via --password (raw value or token:<TOKEN> format) with --sasl-mechanism OAUTHBEARER. (#30169)
  • #30222 Add OAUTHBEARER SASL mechanism support to the admin API endpoint used by rpk debug remote-bundle start, enabling remote debug bundle collection against clusters configured with OAUTHBEARER authentication. (#30225)
  • rpk debug remote-bundle start now supports OAUTHBEARER (OIDC) profiles. Pass the bearer token via --password (or kafka_api.sasl.password in the rpk profile) when sasl.mechanism is OAUTHBEARER. (#30277)
  • Adds a new layout key to the Iceberg translation mode as a config string, in the value section. layout supports nested and flat; flat is the default and matches previous behavior. (#30917)
  • Iceberg translation now supports schema registry contexts. Configure a topic to resolve schemas in a context via the redpanda.schema.registry.context topic property. (#30132)
  • Added per-entity Kafka quota metrics. Set kafka_per_entity_quota_metrics to true (default false, no restart) to expose per-entity throttling and throughput counters for produce, fetch, and partition-mutation quotas. (#30832)
  • Add rpk check as a new managed plugin for production readiness validation. It checks cluster health, broker configuration, security settings, replication factors, licensing, TLS, and Kubernetes resource configuration against the official production readiness checklists. Supports auto-install, upgrade, and uninstall via rpk check install, rpk check upgrade, and rpk check uninstall. (#30146)
  • Add rpk k8s, a new managed plugin for interacting with Redpanda clusters running on Kubernetes. On first use, rpk auto-downloads, checksum-verifies, and caches the plugin; manage it explicitly with rpk k8s install / upgrade / uninstall. (#30833)
  • Added an admin API endpoint to cancel an in-progress controller (raft0) reconfiguration. (#30918)
  • Added redpanda_cluster_health_* Prometheus metrics (public and internal endpoints) exposing the same inputs as rpk cluster health, including nodes_down, leaderless_partitions, under_replicated_partitions, unhealthy_reasons, and a metadata_age_seconds freshness gauge. Disabled by default; enable with the new health_monitor_metrics_enabled cluster property. (#30769)
  • Expose estimated cloud instance hardware capacity (vCPUs, memory, disk, network bandwidth, and IOPS) as Prometheus metrics, derived from the detected cloud instance type. (#30742)
  • rpk --print-tree emits the full rpk command tree as a single JSON document, suited for LLMs and automation. (#30380)
  • rpk redpanda admin broker list now includes a --detailed flag with additional per-path disk usage information, and supports the --format json/yaml flag. (#30096)
  • Added rpk cloud auth token to print the current cloud auth token. (#29964)
  • New metric vectorized_kafka_leadership_changes counts leadership changes in a topic. (#30117)
  • New cluster config oidc_http_proxy_url routes OIDC discovery and JWKS fetches through an HTTP forward proxy. Set to a URL of the form http://host:port or https://host:port to enable; leave unset (the default) to connect to the OIDC endpoint directly. Live-reloadable, no broker restart required. (#30268)
  • New cluster configs oidc_http_proxy_username / oidc_http_proxy_password add HTTP Basic authentication to the OIDC forward proxy; (#30738)
  • New configuration iceberg_rest_catalog_credentials_host: the hostname to connect to for retrieving role-based credentials for the Iceberg REST catalog, for cases where the REST catalog uses a different credentials source than cloud storage. (#30284)
Improvements
  • max_concurrent_producer_ids and max_transactions_per_coordinator now default to 100,000 and 10,000 respectively (previously unlimited), reducing memory usage from accumulated producer state. Existing explicit overrides are unaffected. (#30058)
  • Prevent oversized allocations/OOMs when using a large number of ACLs in Redpanda. (#30967)
  • Prevent oversized allocations in the Kafka layer when using large consumer groups. (#30744)
  • The schema_registry_cache_schema_count metric now includes a type label (AVRO, JSON, PROTOBUF), replacing the single per-context gauge with one gauge per schema type per context. Dashboards or alerts that query this metric without filtering on type should be updated to sum across the label, e.g. sum by (context) (redpanda_schema_registry_cache_schema_count). (#30725)
  • Avoid potential oversized allocations in the segment index materialization path. (#30236)
  • Iceberg Topics will stop creating new Parquet files if there is a large backlog of files not yet committed to the Iceberg catalog, and the Iceberg Topics Coordinator now commits to the catalog in chunks — both changes help avoid an OOM when the catalog has rejected Redpanda commits for a prolonged period. (#30958)
  • Fixed unnecessary memory allocations/deallocations on the L0 write path in Cloud Topics. (#30980)
  • Avoid recompression of unchanged batches in the local storage and Cloud Topics compaction implementation. (#30669)
  • Optimize compaction logic, especially for large batches. (#30740)
  • Optimize the ACL authorization path for all callers (Kafka handlers, schema registry, Pandaproxy, and Iceberg). (#30829)
  • Optimize the segment_meta_cstore::insert_entries() path for the generic append case. (#30601)
  • Adds a kafka_fetch_read_coalescing_enabled cluster property. When enabled, partition reads and serialized responses for high fan-out workloads are shared instead of duplicated across responses. (#31010)
  • Make the fetch path more resilient to errors in single partitions. (#30097)
  • Improve shadowing failover latency on shadow links with large topic counts. (#30089)
  • Improves false positive detection in the cloud storage scrubber to filter out compacted reuploads. (#30062)
  • Added a new cluster property iceberg_default_schema_case_insensitive (yes / no / auto, default auto) that determines whether the Iceberg subsystem compares field names case-insensitively. auto attempts to detect this automatically for AWS Glue, which addresses a sporadic issue where Glue returns field names lower-cased instead of verbatim. (#30459)
  • Purging an Iceberg table managed by the filesystem catalog will now delete all of the table's files, not just the metadata files. (#30691)
  • The Iceberg translation state REST endpoint now returns a partition state entry for every partition of the topic and reports the topic's partition_count. (#30576)
  • The controller leader is now observable on the public metrics endpoint via the new redpanda_raft_leader_for gauge (1 on the controller leader, 0 otherwise). (#30826)
  • Adds the option to configure Schema Registry to use internal RPCs for interacting with the schemas topic, removing the need for explicit authN/Z or ephemeral credentials. (#30046)
  • Alters the behavior of restart-required cluster configs so that changes are invisible to Redpanda internals until a node actually restarts; pending changes and restart status still appear in the admin API as before. (#30109)
  • Better guard against malformed requests when parsing Kafka messages. (#30191)
  • Don't error on potentially unknown cluster properties when issuing removal requests through the admin API. (#30054)
  • Downgraded the "attempted to load identical license, doing nothing" admin API log message from info to debug, reducing log noise when operators or automation reapply the same enterprise license on a schedule. (#30188)
  • #18422 The internal HTTP client (cloud storage, IAM credential refresh, OIDC, metrics reporter) now tries all DNS-resolved addresses when connecting instead of just one, improving connectivity to dual-stack (IPv4/IPv6) endpoints and failing fast when an endpoint is down. (#30796)
  • rpk ai <sub> now reads the active cloud profile's cached AI Gateway URL and only contacts the public API when the cache is empty, removing an extra round trip on every plugin invocation. (#30327)
  • rpk debug bundle now samples /proc/interrupts, /proc/softirqs, and /proc/diskstats twice so support can compute counter deltas. (#30279)
  • rpk redpanda admin is deprecated and folded into rpk cluster. Use rpk cluster brokers for decommission/recommission, rpk cluster info -b --detailed to list brokers, rpk cluster config list --node-id <ID> to query a broker's view of the cluster config, rpk cluster loggers {list,set} to manage broker log levels, and rpk cluster partitions list --node-ids <ID> to filter partitions by broker. (#30332)
  • Redpanda's install setup script now downloads packages from linux.pkg.redpanda.com instead of Cloudsmith. (#30557)
  • Decommission may now cancel a stalled cluster node add. (#30377)
  • Various internal consensus lifecycle improvements. (#31022)
  • Add --format json|yaml|text|help to 20 rpk commands, including cluster maintenance status, cluster config status, profile list, plugin list, and more. (#30194)
  • Add Group: principal support to rpk security role assign/unassign, and remove the explicit --group flag to prevent confusion. (#29987)
  • rpk: all column headers are now standardized to avoid whitespace, using hyphens instead of underscores. (#30310)
  • Updated the default console image version in rpk container commands to v3.8.0. (#30954)
Bug Fixes
  • Patched krb5 against CVE-2026-40355 (null pointer dereference) and CVE-2026-40356 (integer underflow) in NegoEx message parsing, both exploitable by an unauthenticated remote attacker to crash the process (CVSS 8.7). (#30537)
  • Upgraded OpenSSL from 3.5.5 to 3.5.6 to address CVE-2026-31790, which could allow an attacker supplying a malformed RSA public key to trigger use of uninitialized memory during RSA key encapsulation. (#30238)
  • Upgraded OpenSSL from 3.5.6 to 3.5.7 to resolve 10 CVEs (CVE-2026-45447, CVE-2026-45446, CVE-2026-45445, CVE-2026-42770, CVE-2026-42769, CVE-2026-42766, CVE-2026-42764, CVE-2026-34183, CVE-2026-34182, CVE-2026-34180). (#30797)
  • Upgraded libxml2 to v2.15.3 to fix CVE-2026-6732, a type confusion vulnerability in XSD validation. (#30392)
  • Upgraded the base container image from Ubuntu Noble to 24.04 to address a Snyk-flagged vulnerability. (#30694)
  • Security: prevent the default OpenSSL config from being loaded from the host machine (OPENSSL_CONF env var or /etc/ssl/openssl.cnf) in self-hosted installations, ensuring only Redpanda configs control crypto and TLS settings. (#29763)
  • Prevents a potential oversized allocation in Kafka protocol parsing of tagged fields. (#30160)
  • Avoid OOM under memory fragmentation when there are many ACLs. (#30368)
  • Fixed a cloud topics epoch fencing race where a failed epoch bump could later admit a stale-epoch write, poisoning the partition log and crashing all replicas of the partition. (#31110)
  • Fixed a potential broker crash (use-after-free) in the cloud topics metastore when accessing raft state during leadership changes. (#31048)
  • Fixed a cluster membership lock that could occur when a node was decommissioned while being added as a controller (raft0) learner. (#30926)
  • Fixed a reactor stall in the producer state cache when many producers are unevictable due to in-flight requests or open transactions. (#29991)
  • Fixed a rare condition where Tiered Storage metadata spillover could get permanently stuck on partitions with small, frequent segments, leaving orphaned spillover manifest objects in the bucket. (#31081)
  • Fixed internal topics being autocreated with incorrect properties. (#31236)
  • Fixed compaction incorrectly assigning future timestamps to records compacted from strictly-past input. (#30998)
  • #30815 Fixed a raft pre-vote livelock where a follower recovering behind a live leader could repeatedly start elections, leaving partitions under-replicated and stalling acks=all produce with request timeouts. (#30817)
  • Fixes a bug in OffsetForLeaderEpoch handling with tiered topics that could cause consumers to reset their fetch position to the beginning of the log held in cloud storage. (#31060)
  • Fixes a bug in cloud topics compaction that could cause repeated no-op compactions if the topic uses retention or transactions. (#31122)
  • Fixes a bug where Cloud Topics with the compact cleanup policy would have log retention policies applied to them. (#31104)
  • Fixes a bug where fetches against tiered storage could fail when retention advances past all segments and new segments are added. (#30303)
  • Fixes a crash that could occur in the Cloud Topics metastore upon certain errors during metastore database compaction. (#30730)
  • Fixes a hang that could be caused by many concurrent multipart uploads. (#30919)
  • Fixes a potential deadlock arising from a race between raft snapshots and transaction operations. (#30207)
  • Fixes a rare crash due to a race condition between transaction-related operations and partition shutdown. (#30081)
  • Fixes a rare race condition between snapshots and compaction of consumer offset partitions resulting in dangling open transactions. (#30071)
  • Fixes a reactor stall seen when there are a large number of pending files in the Iceberg Topics coordinator. (#30868)
  • Fixes a wedge in multi-output transforms where a produce failure on one output topic silently stalled the processor instead of restarting it. (#30836)
  • Fixes an issue that prevented raft followers across high-RTT links from establishing connections long enough to receive heartbeat request replies. (#30486)
  • Fixes an issue where cluster linking would not replicate the partition start offset. (#30996)
  • Fix an issue where multi-part delete requests were rejected by ABS when using OAuth (unexpected headers). (#30133)
  • Fix an issue where slow replication could cause audit log produce RPCs to pile up effectively unbounded, eventually exhausting memory on the server shard. (#30041)
  • Fix an issue with Cloud Topics garbage collection where deleting all cloud topics could leave stale objects in the bucket forever. (#30200)
  • Fix consumer group lag metrics inflated after retention or trim-prefix. (#30822)
  • Fix consumer group lag metrics reporting 0 for read-replica topics. (#30873)
  • Fixed shadow link replication advancing the shadow partition start offset past the source partition's start offset when a replicator resumes after a shadow partition leadership change. (#30785)
  • Fixed the vectorized_rpc_client_requests_pending gauge drifting over time. (#30264)
  • Fix tiered storage I/O remaining throttled at the previously configured rate after cloud_storage_max_throughput_per_shard was unset. (#30319)
  • Fix an assertion crash in the cloud storage self-test when a multipart upload part failed mid-sequence. (#30344)
  • Fix a process abort when the tiered storage cache's local disk fills up while a segment download is in progress on a non-zero shard. (#30335)
  • Allow combining aws_sigv4 Iceberg REST catalog authentication with the sts cloud credentials source. (#30548)
  • Correctly decode variable-length Avro decimal payloads on the ingest path. (#30516)
  • Fix Iceberg map columns being unreadable from strict Parquet readers (e.g. Apache Spark) due to a missing LogicalType.MAP annotation in the written Parquet schema. (#30454)
  • Fix corruption of negative decimal partition values in Iceberg manifests for decimal columns whose precision does not require 16 bytes (e.g. decimal(10,2)). (#30516)
  • Fix parsing of Iceberg table metadata whose sort orders use the spec-canonical singular source-id field (e.g. metadata produced by Unity Catalog). (#30475)
  • Fix schema evolution incorrectly rejecting new optional Iceberg columns whose nested types contain structurally-required fields (e.g. maps, whose keys are always required). (#30585)
  • Iceberg REST catalog credential refresh requests were being sent to the wrong host when cloud_storage_credentials_host was set; the host override intended for cloud storage was being applied globally. (#30284)
  • The day partition transform now produces a date-typed partition column (matching the Iceberg spec) instead of an integer. (#30515)
  • Fixed Avro schema lookup false negatives when equivalent nested primitive schemas used simple form (e.g. "string") and object form (e.g. {"type":"string"}). (#30565)
  • Fixed schema registry returning a 40403 error when looking up Avro schemas that use unqualified named type references (e.g. "Inner") against registered schemas using fully-qualified references (e.g. "com.example.Inner") within the same namespace. (#30127)
  • #30374 Schema Registry: fixed protobuf compatibility checks incorrectly failing with MESSAGE_REMOVED when a map field is removed. (#30400)
  • #30398 Fixed a bug in the schema registry where adding a new required field to a JSON schema was incorrectly allowed under BACKWARD compatibility mode. (#30525)
  • #30414 Fixed a bug where a double metric registration could occur when STS credentials were used for both Iceberg and Tiered Storage systems. (#30489)
  • Fixed a leak in the Iceberg translation subsystem where per-partition metrics were not released after a partition was removed from a broker. (#30701)
  • Fixed a spurious storage parser.cc — Stopping parser, short read error that could be logged when a segment was flushed concurrently with an in-flight append (e.g. during raft recovery). (#30660)
  • REST proxy and schema registry now return {"error_code": 404, "message": "..."} for unmatched routes, matching the envelope clients already parse. (#30417)
  • Metrics that previously ignored disable_public_metrics (raft_learners_gap_bytes, cluster_members_backend_queued_node_operations, cluster_partition_num_with_broken_rack_constraint) now honor it. (#30720)
  • Changes to cloud_storage_throughput_limit_percent now take effect at runtime instead of being ignored until restart. (#30230)
  • Invalidates LSM iterators when exceptions are thrown. (#30348)
  • admin: GET /v1/cluster/health_overview now always includes nodes_in_recovery_mode, even when empty. (#30640)
  • report Iceberg-disabled topics as DISABLED in the translation_state response. (#30761)
  • rpk/debug/bundle: dedup admin addresses across host forms. (#30403)

Full changelog: https://github.com/redpanda-data/redpanda/compare/v26.2.0-dev...v26.2.1

View originalPermalink
How v26.2.1 went

v26.1.14

Added 1
  • Added a schema_registry_replay_on_startup cluster property (default off) that hydrates the Schema Registry store at broker start-up rather than lazily on the first request
Changed 4
  • Avoid oversized allocations for some of the schema_registry and pandaproxy handler interfaces
  • HTTP Proxy: a consumer group now resumes from its committed offset on a fresh consumer instance instead of re-reading from the earliest available offset
  • Optimize the schema_registry recovery path by caching references when canonicalizing schemas
  • Schema Registry now replays the internal _schemas topic exactly once when recovering on startup, instead of running redundant concurrent replays; cold start of a large registry is significantly faster
Fixed 7
  • Fixed a cloud-topics epoch fencing race where an epoch bump whose replication failed could later admit a stale-epoch write, poisoning the partition log and crashing all replicas of the partition
  • Fixed a bug in OffsetForLeaderEpoch handling with tiered topics which could cause consumers to reset their fetch position to the beginning of the log held in cloud storage
  • Fixed a potential crash in DescribeLogDirs
  • HTTP Proxy: Consumer group fetches no longer fail indefinitely with offset_out_of_range after retention moves a topic's log start offset past 0; the consumer now recovers to the earliest available offset
  • Fixed a raft pre-vote livelock where a follower recovering behind a live leader could repeatedly start elections, leaving partitions under-replicated and stalling acks=all produce with request timeouts
  • Fixed a bug in which internal topics could be auto-created with the wrong topic properties
  • Fixed allocation double free on no-op replication factor changes
Bug Fixes
  • Fixed a cloud-topics epoch fencing race where an epoch bump whose replication failed could later admit a stale-epoch write, poisoning the partition log and crashing all replicas of the partition. by @Lazin in #31140
  • Fixes a bug in OffsetForLeaderEpoch handling with tiered topics which could cause consumers to reset their fetch position to the beginning of the log held in cloud storage. by @WillemKauf in #31074
  • Fixes a potential crash in DescribeLogDirs by @WillemKauf in #31196
  • HTTP Proxy: Consumer group fetches no longer fail indefinitely with offset_out_of_range after retention moves a topic's log start offset past 0; the consumer now recovers to the earliest available offset (auto.offset.reset=earliest). by @bartoszpiekny-redpanda in #31207
  • Lifecycle fix on groups by @joe-redpanda in #31182
  • #30885 Fixed a raft pre-vote livelock where a follower recovering behind a live leader could repeatedly start elections, leaving partitions under-replicated and stalling acks=all produce with request timeouts. by @stevenpall in #30886
  • #31238 Fixes a bug in which internal topics could be auto-created with the wrong topic properties by @WillemKauf in #31239
  • fix allocation double free on no-op rf changes by @joe-redpanda in #31116
Improvements
  • Added a `schema_registry_replay_on_startup` cluster property (default off) that hydrates the Schema Registry store at broker start-up rather than lazily on the first request. by @sjust-redpanda in #31174
  • Avoid oversized allocations for some of the `schema_registry` and `pandaproxy` handler interfaces. by @WillemKauf in #31200
  • HTTP Proxy: a consumer group now resumes from its committed offset on a fresh consumer instance instead of re-reading from the earliest available offset. by @bartoszpiekny-redpanda in #31225
  • Optimize the `schema_registry` recovery path by caching references when canonicalizing schemas by @WillemKauf in #31193
  • Schema Registry now replays the internal `_schemas` topic exactly once when recovering on startup, instead of running redundant concurrent replays; cold start of a large registry is significantly faster. by @sjust-redpanda in #31174

Full Changelog: https://github.com/redpanda-data/redpanda/compare/v26.1.13...v26.1.14

View originalPermalink
How v26.1.14 went

v26.1.13

Added 1
  • Add a new enable_development_metrics cluster configuration false by default runtime configurable that exposes internal_rpc_latency metrics to the internal /metrics endpoint when enabled
Changed 4
  • Iceberg Topics will stop creating new parquet files if there is a large backlog of files not yet committed to the Iceberg catalog to avoid OOM when the catalog has rejected Redpanda commits
  • Optimize the ACL authorization path for all callers including Kafka handlers schema registry Pandaproxy and Iceberg
  • Prevent oversized allocations and OOMs when using a large number of ACLs in Redpanda
  • The Iceberg Topics Coordinator will now commit to the Iceberg catalog in chunks to avoid OOM when the catalog has rejected Redpanda commits
Fixed 9
  • Fix consumer group lag metrics reporting 0 for read-replica topics
  • Fixed a cluster membership lock that could occur when a node was decommissioned while it was being added as a controller raft0 learner
  • Fixed a potential broker crash use-after-free in the cloud topics metastore when accessing Raft state during leadership changes
  • Fixes a bug in cloud topics compaction that could cause repeated no-op compactions if the topic uses retention or transactions
  • Fixes a bug where Cloud Topics with the compact cleanup policy would have log retention policies applied to them
  • Fixes an issue where cluster linking would not replicate the partition start offset
Bug Fixes
  • Fix consumer group lag metrics reporting 0 for read-replica topics. by @bartoszpiekny-redpanda in #30939
  • Fixed a cluster membership lock that could occur when a node was decommissioned while it was being added as a controller (raft0) learner. by @mmaslankaprv in #31091
  • Fixed a potential broker crash (use-after-free) in the cloud topics metastore when accessing Raft state during leadership changes. by @nvartolomei in #31052
  • Fixes a bug in cloud topics compaction that could cause repeated no-op compactions if the topic uses retention or transactions. by @andrwng in #31124
  • Fixes a bug where Cloud Topics with the compact cleanup policy would have log retention policies applied to them. by @andrwng in #31111
  • Fixes an issue where cluster linking would not replicate the partition start offset. by @andrwng in #31000
  • rpk ai no longer requires a selected Redpanda Cloud cluster to run. The AI CLI uses its own rpk ai auth login and rpk ai env use, independent of any rpk cloud session. by @birdayz in #31079
  • fix a latent double get_exception call on a failed future in cloud topics metastore by @oleiman in #31045
Improvements
  • Adds a new enable_development_metrics cluster configuration (false by default, runtime configurable). When enabled, internal_rpc_latency metrics are exposed to the internal /metrics endpoint. This family of metrics can be expensive (large number of series) - leave it set to false to save on metrics scraping costs. by @WillemKauf in #30957
  • Fixes a bug where unnecessary memory allocations/deallocations were being made on the L0 write path in cloud topics by @WillemKauf in #30983
  • Iceberg Topics will stop creating new parquet files if there is a large backlog of files not yet committed to the Iceberg catalog. This helps avoid an OOM when the catalog has rejected Redpanda commits for prolonged periods of time. by @andrwng in #31036
  • Optimize the ACL authorization path for all callers (Kafka handlers, schema registry, Pandaproxy & Iceberg) by @WillemKauf in #30969
  • Prevent oversized allocations/OOMs when using a large number of ACLs in redpanda by @WillemKauf in #30969
  • The Iceberg Topics Coordinator will now commit to the Iceberg catalog in chunks, avoiding an OOM when the catalog has rejected Redpanda commits for prolonged periods of time. by @andrwng in #31036

Full Changelog: https://github.com/redpanda-data/redpanda/compare/v26.1.12...v26.1.13

View originalPermalink
How v26.1.13 went

v26.1.12

Added 1
  • Add stuck raft0 escape hatches
Changed 1
  • Make the schema walk keyword-aware in JSON
Fixed 5
  • Fix a bug in which a generate_report() request to the transform system could result in a nullptr dereference at startup
  • Fix a bug in which a stale read in the l0 write scheduler could result in a division by zero (raising SIGFPE)
  • Fix a reactor stall seen when there are a large number of pending files in the Iceberg Topics coordinator
  • Fix deleted namespace race for REST_HADOOP catalog in datalake
  • Surface worker crashes as descriptive errors in dt/kgo
Bug Fixes
  • Fixes a bug in which a generate_report() request to the transform system could result in a nullptr dereference at startup by @WillemKauf in #30910
  • Fixes a bug in which a stale read in the l0 write scheduler could result in a division by zero (raising SIGFPE). by @WillemKauf in #30920
  • Fixes a reactor stall seen when there are a large number of pending files in the Iceberg Topics coordinator. by @andrwng in #30880
  • PR #30929 [v26.1.x] datalake: Fix deleted namespace race for REST_HADOOP catalog by @wdberkeley
  • PR #30944 [v26.1.x] dt/kgo: surface worker crashes as descriptive errors by @nvartolomei
Improvements
  • adds stuck raft0 escape hatches by @vbotbuildovich in #30945
  • PR #30922 [v26.1.x] [CORE-16282] json: make the schema walk keyword-aware by @mnajda-redpanda

Full Changelog: https://github.com/redpanda-data/redpanda/compare/v26.1.11...v26.1.12

View originalPermalink
How v26.1.12 went

v26.1.11

Added 1
  • rpk --print-tree emits the full rpk command tree as a single JSON document, suited for LLMs and automations
Changed 3
  • Optimize compaction logic, especially for large batches
  • Upgrade openssl to 3.5.7
  • Remove shard aggregation for max_offset and under_replicated_partitions metrics
Fixed 6
  • Fix consumer group lag metrics inflated after retention or trim-prefix
  • Fixed shadow link replication advancing the shadow partition start offset past the source partition's start offset when a replicator resumes after a shadow partition leadership change
  • Fixes a bug in which hung requests to the schema registry or in shadow linking could cause a deadlock during shutdown
  • Fixes a crash that could occur in the Cloud Topics metastore upon certain errors during metastore database compaction
  • Fixes a wedge in multi-output transforms where a produce failure on one output topic silently stalled the processor instead of restarting it
  • Fixed a bug in the schema registry where adding a new required field to a JSON schema was incorrectly allowed under BACKWARD compatibility mode
Security 1
  • Upgrade krb5 to 1.22.2 to address CVE-2026-40355 and CVE-2026-40356 (NegoEx parsing vulnerabilities)
Features
  • rpk --print-tree: emits the full rpk command tree as a single JSON document, suited for LLMs and automations. by @r-vasquez in #30834
Bug Fixes
  • Fix consumer group lag metrics inflated after retention or trim-prefix. by @bartoszpiekny-redpanda in #30870
  • Fixed shadow link replication advancing the shadow partition start offset past the source partition's start offset when a replicator resumes after a shadow partition leadership change. by @Lazin in #30819
  • Fixes a bug in which hung requests to the schema registry or in shadow linking could cause a deadlock during shutdown. by @WillemKauf in #30788
  • Fixes a crash that could occur in the Cloud Topics metastore upon certain errors from during metastore database compaction. by @andrwng in #30775
  • Fixes a wedge in multi-output transforms where a produce failure on one output topic silently stalled the processor instead of restarting it. by @WillemKauf in #30855
  • Upgrade krb5 to 1.22.2 to address CVE-2026-40355 and CVE-2026-40356 (NegoEx parsing vulnerabilities). by @tyson-redpanda in #30874
  • #30561 Fixed a bug in the schema registry where adding a new required field to a JSON schema was incorrectly allowed under BACKWARD compatibility mode. by @TheJohnMatti in #30563
Improvements
  • Optimize compaction logic, especially for large batches. by @WillemKauf in #30760
  • ct/l1: check is_linked() on owner shard by @WillemKauf in #30747
  • build/deps: upgrade openssl to 3.5.7 by @tyson-redpanda in #30813
  • ct/scale: raise fetch concurrency for cloud_topics MPT variants by @oleiman in #30867
  • cluster: remove shard aggregation for max_offset and under_replicated_partitions by @WillemKauf in #30877

Full Changelog: https://github.com/redpanda-data/redpanda/compare/v26.1.10...v26.1.11

View originalPermalink
How v26.1.11 went

v26.1.10

Added 2
  • New live-reloadable cluster configs oidc_http_proxy_username and oidc_http_proxy_password add HTTP Basic authentication to the OIDC forward proxy
  • New cluster property iceberg_default_schema_case_insensitive to determine whether the Iceberg subsystem compares field names case-insensitively, with auto-detection support for AWS Glue catalogs
Changed 7
  • The day partition transform now produces a date-typed partition column instead of int
  • Report Iceberg-disabled topics as DISABLED in translation_state response
  • Avoid recompression of unchanged batches in the local storage and cloud topics compaction implementation
  • Optimize the segment_meta_cstore insert_entries path for the generic append case
  • Prevent oversized allocations in the kafka layer when utilizing large consumer groups
  • Purging an Iceberg table managed by the filesystem catalog will now delete all the table's files, not just the metadata files
  • The iceberg translation state REST endpoint now returns a partition state entry for every partition of the topic and reports the topic's partition_count
Fixed 5
  • Fix schema evolution incorrectly rejecting new optional Iceberg columns whose nested types contain structurally-required fields
  • Fixed Avro schema lookup false negatives when equivalent nested primitive schemas used simple form and object form
  • Fixed a leak in the Iceberg translation subsystem where per-partition metrics were not released after a partition was removed from a broker
  • Fixed a bug in the feature_table where decommissioned nodes holding back the cluster-wide cluster_version prevented cluster_version from being updated
  • Fixed a bug where fetches against tiered storage could fail when retention advances past all segments and new segments are added
Security 1
  • Patched krb5 against CVE-2026-40355 (null pointer dereference) and CVE-2026-40356 (integer underflow) in NegoEx message parsing, exploitable by unauthenticated remote attackers to crash the process
Features
  • New live-reloadable cluster configs oidc_http_proxy_username / oidc_http_proxy_password add HTTP Basic authentication to the OIDC forward proxy (oidc_http_proxy_url); set both to authenticate, leave unset for an anonymous proxy. The password is secret. by @nguyen-andrew in #30767
Bug Fixes
  • Fix schema evolution incorrectly rejecting new optional Iceberg columns whose nested types contain structurally-required fields (e.g. maps, whose keys are always required). by @nvartolomei in #30590
  • Fixed Avro schema lookup false negatives when equivalent nested primitive schemas used simple form, such as "string", and object form, such as {"type":"string"}. by @pgellert in #30641
  • Fixed a leak in the Iceberg translation subsystem where per-partition metrics were not released after a partition was removed from a broker. by @nvartolomei in #30706
  • Fixes a bug in the feature_table in which nodes which are holding back the cluster-wide cluster_version, when decommissioned, result in the cluster_version never being updated until a restart/controller leadership move is forced. by @WillemKauf in #30636
  • Fixes a bug where fetches against tiered storage could fail when retention advances past all segments and new segments are added. by @wdberkeley in #30637
  • Patched krb5 against CVE-2026-40355 (null pointer dereference) and CVE-2026-40356 (integer underflow) in NegoEx message parsing, both exploitable by an unauthenticated remote attacker to crash the process (CVSS 8.7). by @tyson-redpanda in #30572
  • The day partition transform now produces a date-typed partition column (matching the Iceberg spec) instead of int. by @mmaslankaprv in #30534
  • report Iceberg-disabled topics as DISABLED in translation_state response. by @bharathv in #30770
Improvements
  • Added a new cluster property iceberg_default_schema_case_insensitive with possible values of yes, no, or auto, default is auto. This property determines whether the Iceberg subsystem compares field names case-insensitively or not. The auto value means the system will attempt to detect if it should use case insensitive comparison. This will happen if the detected REST catalog is AWS Glue, which addresses a sporadic issue with AWS Glue where it would return field names lower-cased instead of verbatim. by @wdberkeley in #30577
  • Avoid recompression of unchanged batches in the local storage and cloud topics compaction implementation. by @WillemKauf in #30672
  • Optimize the segment_meta_cstore::insert_entries() path for the generic append case. by @WillemKauf in #30610
  • Prevent oversized allocations in the kafka layer when utilizing large consumer groups by @WillemKauf in #30753
  • Purging an Iceberg table managed by the filesystem catalog will now delete all the table's files, not just the metadata files. by @wdberkeley in #30698
  • The iceberg translation state REST endpoint now returns a partition state entry for every partition of the topic and reports the topic's partition_count. by @mmaslankaprv in #30657

Full Changelog: https://github.com/redpanda-data/redpanda/compare/v26.1.9...v26.1.10

View originalPermalink
How v26.1.10 went

v25.3.15

Added 1
  • Add OAUTHBEARER SASL mechanism support to rpk, enabling OIDC-based authentication for the Kafka client, admin API, and schema registry via --password and --sasl-mechanism OAUTHBEARER
Changed 1
  • Backport features_auto_finalization cluster configuration option to allow opting out of automatic upgrade finalization
Fixed 15
  • Allow combining aws_sigv4 Iceberg REST catalog authentication with the sts cloud credentials source
  • Correctly decode variable-length Avro decimal payloads on the ingest path
  • Fix Iceberg map columns being unreadable from strict Parquet readers due to missing LogicalType.MAP annotation in the written Parquet schema
  • Fix a process abort when the tiered storage cache's local disk fills up while a segment download is in progress on a non-zero shard
  • Fix corruption of negative decimal partition values in Iceberg manifests for decimal columns whose precision does not require 16 bytes
  • Fix schema evolution incorrectly rejecting new optional Iceberg columns whose nested types contain structurally-required fields
Security 3
  • Patch krb5 against CVE-2026-40355 (null pointer dereference) and CVE-2026-40356 (integer underflow) in NegoEx message parsing
  • Upgrade OpenSSL from 3.0.19 to 3.0.20 to address CVE-2026-31790, which could allow an attacker supplying a malformed RSA public key to trigger use of uninitialized memory
  • Upgrade libxml2 to v2.15.3 to fix CVE-2026-6732 type confusion vulnerability in XSD validation
Features
  • Add OAUTHBEARER SASL mechanism support to rpk, enabling OIDC-based authentication for the Kafka client, admin API, and schema registry. Pass the token via --password (raw value or token: format) with --sasl-mechanism OAUTHBEARER. by @david-yu in #30312
Bug Fixes
  • Allow combining aws_sigv4 Iceberg REST catalog authentication with the sts cloud credentials source. by @nvartolomei in #30554
  • Correctly decode variable-length Avro decimal payloads on the ingest path. by @nvartolomei in #30518
  • Fix Iceberg map columns being unreadable from strict Parquet readers (e.g. Apache Spark) due to a missing LogicalType.MAP annotation in the written Parquet schema. by @nvartolomei in #30458
  • Fix a process abort when the tiered storage cache's local disk fills up while a segment download is in progress on a non-zero shard. by @nvartolomei in #30352
  • Fix corruption of negative decimal partition values in Iceberg manifests for decimal columns whose precision does not require 16 bytes (e.g. decimal(10,2)). by @nvartolomei in #30518
  • Fix schema evolution incorrectly rejecting new optional Iceberg columns whose nested types contain structurally-required fields (e.g. maps, whose keys are always required). by @nvartolomei in #30591
  • Fix tiered storage I/O remaining throttled at the previously-configured rate after cloud_storage_max_throughput_per_shard was unset. by @nvartolomei in #30472
  • Fixed Avro schema lookup false negatives when equivalent nested primitive schemas used simple form, such as "string", and object form, such as {"type":"string"}. by @pgellert in #30642
  • Fixed schema registry returning 40403 when looking up Avro schemas that use unqualified named type references (e.g. "Inner") against registered schemas using fully-qualified references (e.g. "com.example.Inner") within the same namespace. by @ksitnik-tc in #30267
  • Fixed the vectorized_rpc_client_requests_pending gauge drifting over time. by @nvartolomei in #30297
  • Fixes a bug in the feature_table in which nodes which are holding back the cluster-wide cluster_version, when decommissioned, result in the cluster_version never being updated until a restart/controller leadership move is forced. by @WillemKauf in #30634
  • Fixes a bug where fetches against tiered storage could fail when retention advances past all segments and new segments are added. by @wdberkeley in #30639
  • Fixes an issue that prevented raft followers across high-RTT links from establishing connections long enough to receive heartbeat request replies. by @ballard26 in #30550
  • Patched krb5 against CVE-2026-40355 (null pointer dereference) and CVE-2026-40356 (integer underflow) in NegoEx message parsing, both exploitable by an unauthenticated remote attacker to crash the process (CVSS 8.7). by @tyson-redpanda in #30571
  • Upgraded OpenSSL from 3.0.19 to 3.0.20 to address CVE-2026-31790, which could allow an attacker supplying a malformed RSA public key to trigger use of uninitialized memory during RSA key encapsulation. by @tyson-redpanda in #30239
  • Upgraded libxml2 to v2.15.3 to fix CVE-2026-6732 type confusion vulnerability in XSD validation. by @tyson-redpanda in #30394
  • #30439 Schema Registry: fixed protobuf compatibility checks incorrectly failing with MESSAGE_REMOVED when a map field is removed. by @QueLLL in #30440
  • #30504 Fixes a bug in which a double metric registration could occur when sts credentials were used for both iceberg and tiered_storage systems. by @WillemKauf in #30505
  • cluster: fix enterprise validation for iceberg enablement by @WillemKauf in #30526
  • datalake: stop bucketing unknown_error as file_io_error by @nvartolomei in #30617
Improvements
  • Backport features_auto_finalization cluster configuration option to allow opting out of automatic upgrade finalization before upgrading to v26.2. by @dotnwat in #30461
  • Optimize the segment_meta_cstore::insert_entries() path for the generic append case. by @WillemKauf in #30609
  • #30270 Avoid potential oversized allocations in the segment index materialization path by @WillemKauf in #30274
  • Avoid oversized alloc in compaction reducers by @StephanDollberg in #30218
  • Validate iceberg_rest_catalog_endpoint at config time by @WillemKauf in #30569
  • Trace schema evolution inputs by @nvartolomei in #30603

Full Changelog: https://github.com/redpanda-data/redpanda/compare/v25.3.14...v25.3.15

View originalPermalink
How v25.3.15 went

v26.1.9

Added 1
  • Backport features_auto_finalization cluster configuration option to allow opting out of automatic upgrade finalization
Fixed 7
  • Allow combining aws_sigv4 Iceberg REST catalog authentication with the sts cloud credentials source
  • Correctly decode variable-length Avro decimal payloads on the ingest path
  • Fix corruption of negative decimal partition values in Iceberg manifests for decimal columns whose precision does not require 16 bytes
  • Fix parsing of Iceberg table metadata whose sort orders use the spec-canonical singular source-id field
  • Fix tiered storage I/O remaining throttled at the previously-configured rate after cloud_storage_max_throughput_per_shard was unset
  • Fix raft followers across high-RTT links from establishing connections long enough to receive heartbeat request replies
  • Fix double metric registration when sts credentials were used for both iceberg and tiered_storage systems
Bug Fixes
  • Allow combining aws_sigv4 Iceberg REST catalog authentication with the sts cloud credentials source. by @nvartolomei in #30553
  • Correctly decode variable-length Avro decimal payloads on the ingest path. by @nvartolomei in #30517
  • Fix corruption of negative decimal partition values in Iceberg manifests for decimal columns whose precision does not require 16 bytes (e.g. decimal(10,2)). by @nvartolomei in #30517
  • Fix parsing of Iceberg table metadata whose sort orders use the spec-canonical singular source-id field (e.g. metadata produced by Unity Catalog). by @mmaslankaprv in #30477
  • Fix tiered storage I/O remaining throttled at the previously-configured rate after cloud_storage_max_throughput_per_shard was unset. by @nvartolomei in #30473
  • Fixes an issue that prevented raft followers across high-RTT links from establishing connections long enough to receive heartbeat request replies. by @ballard26 in #30549
  • #30502 Fixes a bug in which a double metric registration could occur when sts credentials were used for both iceberg and tiered_storage systems. by @WillemKauf in #30503
Improvements
  • Backport features_auto_finalization cluster configuration option to allow opting out of automatic upgrade finalization before upgrading to v26.2. by @dotnwat in #30460
  • PR #30507 cloud_topics/l1: fix UB in db_domain_manager error-logging paths by @Lazin
  • PR #30509 storage: don't override with shard_local_cfg() in ntp_config helpers by @WillemKauf
  • PR #30527 cluster: fix enterprise validation for iceberg enablement by @WillemKauf
  • PR #30540 ct/l1: guard stop_collecting_logs() on local_is_initialized() by @WillemKauf
  • PR #30542 rpk: bump Go to 1.26.3, x/net to v0.54.0 (Snyk findings) by @twmb

Full Changelog: https://github.com/redpanda-data/redpanda/compare/v26.1.8...v26.1.9

View originalPermalink
How v26.1.9 went

v26.1.8

Added 1
  • New configuration option iceberg_rest_catalog_credentials_host to specify the hostname for retrieving role-based credentials for the Iceberg REST catalog
Fixed 7
  • Avoid out-of-memory errors under memory fragmentation when there are many ACLs
  • Fix Iceberg map columns being unreadable from strict Parquet readers due to missing LogicalType.MAP annotation in the written Parquet schema
  • Fix Cloud Topics garbage collection leaving stale objects in the bucket when deleting all cloud topics
  • Fix Iceberg REST catalog credential refresh requests being sent to the wrong host when cloud_storage_credentials_host was set
  • Fix Schema Registry protobuf compatibility checks incorrectly failing with MESSAGE_REMOVED when a map field is removed
  • Fix rpk debug bundle deduplication of admin addresses across host forms
  • Cap fetch memory allocation at max message size limit
Security 1
  • Upgrade libxml2 to v2.15.3 to fix CVE-2026-6732 type confusion vulnerability in XSD validation
Features
  • New configuration: iceberg_rest_catalog_credentials_host: The hostname to connect to for retrieving role-based credentials for the Iceberg REST catalog. May be required when the REST catalog uses a different credentials source than cloud storage — for example, if cloud storage is configured to use STS with a custom credentials host, but the REST catalog uses aws_instance_metadata, this should be set to 169.254.169.254 to prevent the cloud storage host override from applying to catalog credential requests. by @wdberkeley in #30446
Bug Fixes
  • Avoid OOM under memory fragmentation when there are many ACLs. by @pgellert in #30401
  • Fix Iceberg map columns being unreadable from strict Parquet readers (e.g. Apache Spark) due to a missing LogicalType.MAP annotation in the written Parquet schema. by @nvartolomei in #30457
  • Fix an issue with Clout Topics garbage collection where deleting all cloud topics could leave stale objects in the bucket, forever. by @oleiman in #30283
  • Iceberg REST catalog credential refresh requests were sent to the wrong host when cloud_storage_credentials_host was set. The host override intended for cloud storage was applied globally, causing catalog credential fetches to fail if the catalog used a different credentials source with a different expected endpoint. by @wdberkeley in #30446
  • Upgraded libxml2 to v2.15.3 to fix CVE-2026-6732 type confusion vulnerability in XSD validation. by @tyson-redpanda in #30393
  • #30437 Schema Registry: fixed protobuf compatibility checks incorrectly failing with MESSAGE_REMOVED when a map field is removed. by @QueLLL in #30438
  • rpk/debug/bundle: dedup admin addresses across host forms by @hidalgopl in #30411
  • PR #30313 kafka/server: cap fetch memory allocation at max message size limit by @ballard26

Full Changelog: https://github.com/redpanda-data/redpanda/compare/v26.1.7...v26.1.8

View originalPermalink
How v26.1.8 went
View all

Discussion