• /
  • EnglishEspañolFrançais日本語한국어Português
  • ログイン今すぐ開始

Pipeline Control Gateway v2.4.1

May 29, 2026

Configuration-only mode (without Flux)

  • You can now install and operate Pipeline Control gateway without requiring Flux controllers in your cluster. In this mode, New Relic continues to manage your pipeline configuration (sampling, filtering, transforms) automatically through the UI, while you manage gateway infrastructure (scaling, versions) manually via Helm.
  • This reduces the permissions footprint from cluster-admin to namespace-scoped ConfigMap access only, making it suitable for security-restricted and compliance-driven environments.
  • A built-in config-watcher sidecar automatically detects configuration changes pushed from the UI and restarts gateway pods — no external operators (such as Stakater Reloader) required.
  • For installation instructions, refer to Install gateway without Flux.

DaemonSet deployment mode

  • Added support for deploying the gateway as a Kubernetes DaemonSet (one pod per node) instead of a Deployment with HPA. This is useful for environments that require node-level telemetry processing or consistent per-node resource allocation.
  • Enable DaemonSet mode by setting daemonset.enabled: true in your Helm values. The DaemonSet mode also supports the config-watcher sidecar and customConfigMap for configuration-only installations.
  • DaemonSet and Deployment modes are mutually exclusive — the chart uses conditional guards to ensure only one mode is active at a time.
Copyright © 2026 New Relic株式会社。

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.