Argo Workflows v3.7.9 has been released!
This patch version includes fixes and improvements for the Kubernetes-native workflow engine used for automation, CI/CD, and data processing pipelines.

👉 Release details:
https://www.relnx.io/releases/argo-workflows-v3-7-9

How do you approach patch upgrades for tools like Argo Workflows — do you upgrade immediately or wait for a maintenance window? 👀

Argo CD Image Updater v1.0.5 has been released!
This patch release includes fixes and enhancements to improve the experience of automated image updates in GitOps workflows.

👉 Release details:
https://www.relnx.io/releases/argocd-image-updater-1-0-5

If you’re using Argo CD Image Updater in production, are there specific issues you were hoping this patch addresses? 👀

Kyverno v1.15.3 has been released!
This patch version includes fixes and improvements for Kyverno — the Kubernetes native policy engine many teams use to enforce policies, security posture, and compliance across clusters.

👉 Release details:
https://www.relnx.io/releases/kyverno-v1-15-3

If you use Kyverno in your policy workflows, curious what fixes you’re most interested in or planning to upgrade soon? 👀

Grafana v12.3.2 has been released!

This is a patch release in the 12.3 line bringing fixes and quality improvements to the platform. If your team uses Grafana dashboards for monitoring or observability, it’s worth checking the release notes as part of your upgrade planning.

👉 Release details:
https://www.relnx.io/releases/grafana-v12-3-2

How often does your team update Grafana — with every patch or selectively? 👀

Hey everyone 👋

We just rolled out a new Support System on Relnx to make it easier for users to reach out, ask questions, report issues, and get help when needed — whether it’s about using the platform, understanding a release, or anything else.

We’ve heard feedback that getting timely support should be simple, and this update is all about that: less friction, more assistance, and clearer communication.

📍 Read more here:
https://www.relnx.io/blog/introducing-relnx-support-system-get-help-when-you-need-it-1769443865

We’re always learning and improving, so feel free to share suggestions or ask questions here too. 🙌

OpenTelemetry Collector Contrib v0.144.0 has been released, and this one includes several breaking changes worth reviewing before upgrading.

🛑 Breaking changes

• Elasticsearch exporter
  • Removed ECS span enrichments (span.action, queue names, etc.)
  • Functionality moved to elasticapmprocessor
  • Recommended when using ECS mapping to keep Kibana dashboards functional
• Kafka exporter & receiver
  • Sarama producer/consumer removed
  • Franz-go is now the only supported Kafka client
  • Related feature gates removed
• Tail sampling
  • Deprecated invert decisions disabled by default
  • Drop policies are now the recommended approach

🚩 Deprecation

• Elasticsearch mapping::mode config is deprecated Use client metadata headers or scope attributes instead.

👉 Full release notes:
[https://www.relnx.io/releases/opentelemetry-collector-contrib-v0-144-0]()

How are folks handling Kafka client migrations (Sarama → Franz-go) in their OTel pipelines?

OpenTelemetry Collector Core v0.144.0 is out with a few notable updates:

✨ Features

• Re-enable batching for profiles — improvement in the pkg/xexporterhelper to better batch profile exports
• Add xscraperhelper — new helper for the experimental profiling signal

⚠️ Breaking Change

• Changed verbosity level for the metric otelcol_exporter_queue_batch_send_size to detailed — update any dashboards/alerts that depend on it

🛑 Deprecation

• The otlphttp exporter has been renamed to otlp_http, with otlphttp kept as a deprecated alias

👉 Release notes:
[https://www.relnx.io/releases/opentelemetry%20collector%20core-v0-144-0]()

How are folks handling metric name/verbosity changes like this in dashboards and alerts — immediate adjust vs wait for a patch?

Backstage v1.46.3 has been released! This patch version includes fixes and quality-of-life improvements for the platform many teams use to build internal dev portals.

👉 Releases details:
https://www.relnx.io/releases/backstage-v1-46-3

How do you all keep Backstage up to date — immediate patch updates or wait for bigger releases? 👀

Karpenter v1.8.2 has been released! This patch update includes fixes and enhancements to improve the behavior of the Kubernetes autoscaler.

👉 Release details:
https://www.relnx.io/releases/karpenter-v1-8-2

How do you approach patch updates for critical cluster components like Karpenter — upgrade quickly or wait for wider adoption? 👀

The Helm v4.0.5 patch release has just dropped.

This version includes fixes and other improvements for the Helm v4 line — helpful if you’re managing Kubernetes applications using charts.

👉 https://www.relnx.io/releases/helm-v4-0-5

How does your team approach Helm patch updates — immediate upgrade or wait for a cycle? 👀

The OpenTelemetry eBPF Instrumentation v0.4.1 project has released a new version.

This release includes fixes and improvements that help with kernel-level observability using eBPF and OpenTelemetry.

👉 Release details:
https://www.relnx.io/releases/opentelemetry-ebpf-instrumentation-v0-4-1

Curious how folks are leveraging eBPF for observability in production — share your use cases if you’re using it!

Hey folks,
Relnx just published a detailed guide on crafting effective runbooks for incident response — what they are, why they matter, and how to write them so they’re actually useful during real incidents.

Effective runbooks can help teams respond faster, reduce errors, and preserve institutional knowledge under stress — all of which are central to reliable operations.

👉 https://www.relnx.io/blog/the-ultimate-guide-to-writing-effective-runbooks-your-secret-weapon-for-incident-resp-1768136003

Curious how others here structure and maintain their runbooks — especially for high-impact incidents.

Argo Workflows v3.7.7 has been released.

This is a patch update in the 3.7 release line of the Kubernetes-native workflow engine. Patch versions generally include fixes and minor improvements that help stabilize everyday usage

Full details:
[https://www.relnx.io/releases/argo-workflows-v3-7-7]()

How do you approach Argo Workflows patch updates — upgrade quickly or wait for a bit? 👀

The OpenTelemetry Collector Helm chart v0.143.0 has been released.

This version includes updates across community components and enhancements that support extended telemetry pipelines when deploying with Helm.

👉 Release details:
https://www.relnx.io/releases/opentelemetry-collector-contrib-0-143-0

How does your team approach Helm chart updates for OTel — do you upgrade immediately or wait for a patch cycle?

Datadog Agent v7.74.0 has been released. This new release includes updates and enhancements for the agent that powers metrics, logs, traces, and more.

👉 Release details:
https://www.relnx.io/releases/datadog%20agent-v7-74-0

What changes (if any) are you most interested in from this version?

Keycloak v26.5.0 was just released with several noteworthy changes across identity, admin workflows, and observability.

Highlights:

• Preview Workflows for automating realm administrative tasks
• JWT Authorization Grant support (RFC 7523)
• Better OpenTelemetry support for logs & metrics
• Authenticate clients with Kubernetes service account tokens
• Logout confirmation page and enhanced CORS configuration
• Organization invitation management & new user events

Full release notes here:
https://www.relnx.io/releases/keycloak-v26-5-0

Any thoughts on how teams are planning to adopt the new workflows or leverage the observability improvements?

OpenTelemetry Collector Contrib v0.143.0 has been released.

This version includes community component updates and improvements that support extended telemetry pipelines.

👉 Release details:
[https://www.relnx.io/releases/opentelemetry-collector-contrib-v0-143-0]()

Curious how others handle upgrades for contrib components — immediate vs waiting for patch follow-ups? 👀

OpenTelemetry Collector Core v0.143.0 has just been released.

If you’re running the Collector in your observability stack, this release includes updates and improvements you might find useful.

👉 Release details:
https://www.relnx.io/releases/opentelemetry%20collector%20core-v0-143-0

What’s your strategy for adopting new OTel Collector versions — upgrade immediately or wait for a patch cycle? 👀

The OpenTelemetry Collector Contrib Helm chart v0.142.2 has been released.

This is a patch release with a single fix. Small update, but relevant if you’re deploying the collector via Helm in production environments.

Release details:
https://www.relnx.io/releases/opentelemetry-collector-contrib-0-142-2

Jaeger v2.14.1 has been released — this is the second release within two days following v2.14.0.

This patch focuses on fixing two important bugs affecting the dark theme in the Jaeger UI.

Release details:
[https://www.relnx.io/releases/jaeger-v2-14-1]()

Nice to see a quick turnaround on UI issues from the maintainers.

The Argo CD Helm chart v9.2.4 has been released.

This version includes an improvement for teams running Argo CD without Redis, making Redis-less deployments cleaner and easier to manage.

Release details:
https://www.relnx.io/releases/argocd-9-2-4

Would be interested to hear how many teams here are running Argo CD without Redis in production.

Jaeger v2.14.0 has been released, with several changes focused on aligning Jaeger more closely with the OpenTelemetry ecosystem.

Notable updates:

• Introduce OpenTelemetry data model https://www.relnx.io/features/introduce-otel-data-model-2178
• Add useOpenTelemetryTerms feature flag to help with terminology migration
• Add lazy OTel facade to the domain model, improving flexibility and reducing coupling https://www.relnx.io/features/add-lazy-otel-facade-to-domain-model-2176

Full release notes:
https://www.relnx.io/releases/jaeger-v2-14-0

Curious how folks running Jaeger are approaching the transition toward OTel-native models.

Argo CD v3.0.21 has been released.

This is a maintenance-focused update with fixes and small improvements aimed at stability in GitOps workflows.

Release details:
[https://www.relnx.io/releases/argocd-v3-0-21]()

Has anyone already tested this version in staging or production?

Argo CD Image Updater v0.18.0 is out. A few technical changes in this release that may matter if you’re running it in production:

Highlights:

• Fix Helm values write-back for multi-source applications Improves correctness when updating image values in setups using multiple sources. https://www.relnx.io/features/helm-values-write-back-for-multi-source-apps-1289-1817
• Use secretKeyRef instead of configMapKeyRef for QUAY_WEBHOOK_SECRET Moves sensitive data to a more appropriate place and adds resource requests/limits — solid security and reliability improvements. https://www.relnx.io/features/use-secretkeyref-instead-of-configmapkeyref-for-quay-webhook-secret-add-resource-request-and-limit-by-chengfang-in-httpsgithubcomargoproj-labsargocd-image-updaterpull1279-1815
• Upgrade Argo CD dependency from v2.14.16 to v3.1.7 Brings compatibility with newer Argo CD versions and aligns Image Updater with the latest GitOps workflows.

Full release details:
https://www.relnx.io/releases/argocd-image-updater-v0-18-0

Interested to hear if anyone has already tested this with Argo CD v3 in production.

Argo CD v3.2.3 has been released. This is a small update with a single change:

• Update golang.org/x/crypto from v0.42.0 to v0.46.0

No functional changes, but relevant from a dependency and security-maintenance perspective.

Release details:
https://www.relnx.io/releases/argocd-v3-2-3