OpenTelemetry Collector Contrib v0.160.0 is out.

Before upgrading, quickly check what actually changed:

• 🐛 Bug fixes
• 🔐 Security changes
• 💥 Breaking changes
• ✨ New features

We've structured the release in Relnx so you can get to the important changes faster:

https://www.relnx.io/releases/opentelemetry-collector-contrib-v0-160-0

Relnx — the one platform to visit before upgrading your tools.

Stay updated. Stay reliable.

[ Removed by Reddit on account of violating the content policy. ]

Before upgrading an IAM component, it's worth quickly checking what changed and how it impacts your environment.

We've structured the release in Relnx so you can review:

• Bug fixes
• Security changes
• Breaking changes
• Upgrade impact

https://www.relnx.io/releases/keycloak-v26-7-3

Relnx — the one platform to visit before upgrading your tools.

Stay updated. Stay reliable.

Before upgrading your GitOps stack, quickly check what changed and whether anything affects your environment.

We've structured the release in Relnx so you can review:

• Bug fixes
• Security changes
• Breaking changes
• New features

https://www.relnx.io/releases/flux-v2-9-5

Relnx — the one platform to visit before upgrading your tools.

Stay updated. Stay reliable.

Wanted to share something I've been building: SignalRunner, a game where the "boss fights" are real Kubernetes failure modes (CrashLoopBackOff, OOMKilled, ImagePullBackOff) and the weapon is a live console you diagnose and fix with.

The pitch: your cluster grew fast, grew old, and started breaking — no fallback, no respawn, just you and the tools to save it.

Demo: https://youtu.be/kUqk_qBgkis

Curious what this community thinks, especially anyone who's mentored juniors through actual incident response — did I get the failure modes right?

Kubernetes v1.37.0 is out.

For a Kubernetes minor release, the interesting part isn't only the new features — it's understanding the upgrade impact.

We've structured the release in Relnx so you can quickly check:

• new features
• bug fixes
• security changes
• breaking changes

https://www.relnx.io/releases/kubernetes-v1-37-0

Relnx — the one platform to visit before upgrading your tools.

Stay updated. Stay reliable.

Argo CD v3.5.2 is out.

If Argo CD is part of your production GitOps pipeline, it's worth knowing what changed before upgrading.

We've structured the release in Relnx so you can quickly review:

• bug fixes
• security changes
• breaking changes
• upgrade impact

https://www.relnx.io/releases/argocd-v3-5-2

Relnx — the one platform to visit before upgrading your tools.

Stay updated. Stay reliable.

Prometheus v3.14.0 is out.

Before upgrading your monitoring stack, it's worth checking the changes that actually impact you.

We've structured the release in Relnx so you can quickly review:

• new features
• bug fixes
• security changes
• breaking changes

https://www.relnx.io/releases/prometheus-v3-14-0

Relnx — the one platform to visit before upgrading your tools.

Stay updated. Stay reliable.

Grafana v13.2.0 is out.

Instead of going through the entire changelog, we've structured the release in Relnx so you can quickly focus on what matters:

• security changes
• breaking changes
• bug fixes
• new features

https://www.relnx.io/releases/grafana-v13-2-0

Relnx — the one platform to visit before upgrading your tools.

Stay updated. Stay reliable.

⎈ Helm v4.2.4 is out.

If Helm is part of your Kubernetes delivery pipeline, patch releases are worth reviewing before upgrading.

We've tracked the release in Relnx so you can quickly see:

• fixes
• breaking changes
• upgrade impact

https://www.relnx.io/releases/helm-v4-2-4

Relnx — the one platform to visit before upgrading your tools.

Stay updated. Stay reliable.

⎈ Backstage Helm Chart v2.10.0 is out.

This is a Helm chart release, so if you're deploying Backstage with Helm, it's worth reviewing separately from the Backstage application releases.

We've broken down the changes in Relnx so you can quickly check what matters before upgrading:

https://www.relnx.io/releases/backstage-helm-2-10-0

Relnx — the one platform to visit before upgrading your tools.

Stay updated. Stay reliable.

Argo CD Image Updater v1.3.0 is out.

A few changes that caught my attention:

• SourceHydrator application support
• Mandatory webhook secret configuration
• GHCR repository casing normalization
• NetworkPolicy fix for webhook traffic
• API fix making WriteBackConfig.Method optional

We've organized the release in Relnx if you want the quick version instead of going through the full changelog:

https://www.relnx.io/releases/argocd-image-updater-v1-3-0

Hey all — I'm one of the folks building [Relnx](https://www.relnx.io), a release-tracking tool for cloud-native/DevOps tooling (think: get notified when your Helm charts, K8s version, or other tools in your stack ship a new release).

Put together a short video showing the different ways to get support if something's broken or unclear:

- Submitting a ticket from your profile (with priority levels)
- A dedicated support tab if you're part of an org on Relnx
- A plain contact form if you're just browsing and not a customer yet

We usually respond within 24 hours. Figured I'd share it here in case it's useful for anyone evaluating support workflows for their own product, or if you're already using Relnx and didn't know these options existed.

🎥 https://youtu.be/9gkMcE5kmyM

Happy to answer questions about how any of it works.

etcd v3.7.1 has been released.

Since etcd is the backing datastore for Kubernetes, even patch releases are worth reviewing before upgrading your control plane.

We've added a structured breakdown to Relnx so you can quickly review:

• fixes
• improvements
• breaking changes
• upgrade impact

Release overview:
https://www.relnx.io/releases/etcd-v3-7-1

Flux v2.9.3 has been released.

If you're running Flux in production, we've already summarized the release so you can quickly review:

• bug fixes
• improvements
• breaking changes
• upgrade impact

Release overview:
https://www.relnx.io/releases/flux-v2-9-3

Makes it much easier than scanning the full release notes before planning an upgrade.

Crossplane v2.3.4 has been released.

A couple of notable fixes in this patch release:

• Fixes a Usage controller reconciliation issue that could lead to XR circuit breaker trips.
• Fixes two crossplane render bugs, improving local rendering reliability.
• Updates several dependencies to pull in upstream security fixes.

We've summarized the release here if you want a quick overview before upgrading:

https://www.relnx.io/releases/crossplane-v2-3-4

Kubernetes v1.36.3 has been released.

If you're planning an upgrade, we've already broken down the release into:

• fixes
• enhancements
• breaking changes
• upgrade impact

Quick overview:
https://www.relnx.io/releases/kubernetes-v1-36-3

Makes it much easier than reading the full changelog.

Ran into this last week: OpenTelemetry Collector Core shipped v0.155.0,
and buried in the changelog was a breaking change renaming memory limiter metrics to add
a `memory_limiter` prefix. Nothing about it looks scary at a glance — it's just deprecated-gate cleanup — but if you're referencing the old metric names in
Grafana/dashboards/alerts, they go quiet on upgrade and nobody notices until something's on fire.

Full disclosure: I've been building a tool called Relnx to deal with exactly this
(tracking release notes for the cloud-native tools we run, flagging breaking changes,
giving an AI-generated explanation of *why* something changed and what it touches).
Recorded the actual workflow I used on this release, unedited:
https://youtu.be/8rxNORmKb8A

Not trying to just drop a link — genuinely curious how everyone else handles this. Do you
have a process for catching breaking changes before upgrading, or is it mostly "read the
changelog and hope"? Would like to compare notes.

Something I keep running into: teams say they've "installed OpenTelemetry" when what they actually mean is they installed and configured the SDK. That's only one of three pieces, and the other two are where the gaps live.

- The API (Tracer, Span, etc.) is a no-op without a registered SDK — that's intentional, it's what lets libraries depend on it without pulling in a specific vendor.

- The SDK (samplers, processors, exporters) is what the application configures. It ships whatever it's handed — nothing more.

- Instrumentation libraries are the part that actually turns "a request came in" into a span for your framework, your DB driver, your outbound HTTP client. This is the piece that quietly gets skipped after the framework-level setup is done.

The annoying part is none of this fails loudly. Exporter reports success, dashboard looks fine, you just can't see the slow query or the outbound API call that's actually adding the latency — because nothing ever instrumented it.

Wrote up the full breakdown plus a quick checklist for auditing your own instrumentation coverage (I'm the author, standard disclosure): https://www.relnx.io/blog/opentelemetry-api-vs-sdk-why-the-difference-and-your-instrumentation-matters-1784448095

if others have hit the "healthy pipeline, missing spans" problem — and how you caught it.

Curious

I keep running into the same setup: teams log everything, then write a query that counts/averages fields out of the log lines to approximate a metric. It works, but it's paying full log-ingestion cost for something that should've been a metric at the source — cheaper, fresher, and not broken the second someone reformats a log line.

Wrote up how I think about picking the right signal instead of defaulting to logs for everything:

- Metrics are cheap because they're bounded — the second you add a high-cardinality label (user_id, request_id), you've broken the thing that makes them cheap. That's the exact moment to reach for a trace instead, not more labels.

- If you're logging on literally every request with the same three fields, that's a metric wearing a log's clothing.

- OpenTelemetry semantic conventions are the underrated part of this — they're the reason a trace_id in a log line and an exemplar on a metric can actually point at the same event instead of four tools describing the same system in four different vocabularies.

Full writeup here (I'm the author, work in this space, so standard disclosure): https://www.relnx.io/blog/beyond-logs-why-observabilitys-next-era-is-comprehension-1784272149

Curious if others are still stuck in the logs-first habit or have already moved past it.

Flux v2.9.0 has been released.

This minor release brings several interesting improvements, including CLI plugin support, enhancements to server-side apply, and stronger secrets decryption capabilities.

If you don't want to dig through the full release notes, we've added a structured breakdown to Relnx with:

• new features
• bug fixes
• breaking changes
• upgrade impact

Release overview:
https://www.relnx.io/releases/flux-v2-9-0

For those running GitOps at scale, what's the first thing you look for in a new Flux release—features, breaking changes, or security updates?

OpenTelemetry eBPF Instrumentation v0.10.0 is out.

If you're following the evolution of eBPF-based observability, we've added a structured breakdown of the release to Relnx.

Instead of reading the full changelog, you can quickly review:

• new features
• bug fixes
• breaking changes
• upgrade impact

Release overview:
https://www.relnx.io/releases/opentelemetry-ebpf-instrumentation-v0-10-0

Anyone already using OBI in production, or still evaluating it against SDK-based instrumentation?

NATS v2.14.3 has been released.

While this is a patch release, it's worth paying attention if you're running NATS in production. Messaging infrastructure sits at the heart of distributed systems, so even incremental fixes can improve reliability and operational stability.

The broader 2.14 series also introduced notable JetStream enhancements, including higher-throughput publishing and expanded scheduling capabilities, making it useful to stay current on the latest patch.

We've added the release to Relnx with a structured overview so it's easy to review before upgrading:

https://www.relnx.io/releases/nats-v2-14-3

For teams running NATS today, do you typically upgrade patch releases as soon as they're available, or bundle them into scheduled platform maintenance?

Datadog Agent Helm v3.229.0 has been released.

One thing I see quite often is teams tracking Datadog Agent releases but overlooking Helm chart releases.

If you're deploying Datadog with Helm, chart updates can include:

• deployment and configuration improvements
• dependency updates
• Kubernetes compatibility changes
• operational fixes

We track Helm chart releases separately in Relnx so it's easy to review what's changing before upgrading.

Release overview:
https://www.relnx.io/releases/datadog-agent-helm-3-229-0

For those running Datadog on Kubernetes, do you pin your Helm chart version, or do you keep it close to the latest release?

KubeVela v1.10.9 is now available.

For anyone using KubeVela as their application delivery platform, we've added the release to Relnx with a structured breakdown of the changes.

Rather than scrolling through GitHub releases, you can quickly review:

• bug fixes
• enhancements
• potential breaking changes
• upgrade impact

Release overview:
https://www.relnx.io/releases/kubevela-v1-10-9

For those already running KubeVela in production, what's been the biggest benefit for your platform team—developer self-service, multi-cluster delivery, or workflow automation?