The easiest way to install the Kubernetes integration is to use our automated installer to generate a manifest. It bundles not just the integration DaemonSets, but also other New Relic Kubernetes configurations, like Kubernetes events, Prometheus OpenMetrics, and New Relic log monitoring.
As a Kubernetes user, you might consider Auto-telemetry with Pixie for deeper insights into your Kubernetes clusters and workloads. No language agents required.
Ready to get started? If you don't already have one, sign up for a New Relic account. It's free, forever!
We encourage you to use our automated installer for servers, VMs, and unprivileged environments. The automated installer can provide you either a Helm command with the required values filled, or a plain manifest if you don't want to use Helm. It also features great customizability and full control over which features and dependencies are enabled. If you are installing our integration on a managed cloud, please take a look at these preliminary notes before proceeding.
Before you start the installer, make sure you have a New Relic account. It's free and no credit card is required.
If your New Relic account is in the EU region, choose the EU install option.
Alternatively, you can also check our manual instructions for deploying our integration using Helm.
Before starting our automated installer, check out these notes for your managed services or platforms:
Our Kubernetes integration is under active development and we regularly release updates which include bug fixes, new features, and support for newer Kubernetes versions and cloud providers. We strongly recommend all our customers to regularly update the Kubernetes integration to get the best experience.
In order to update an installation that was deployed using Helm command provided by the automated installer, just go through the process and run the Helm command again. This will pull the new version of the chart and its dependencies and upgrade it to the latest version.
We encourage you to deploy our integration using Helm, as it provides a cleaner upgrade path compared to using manifests directly.
If custom manifests have been used instead of Helm, you will need to first remove the old installation using
kubectl delete -f previous-manifest-file.yml, and then proceed through the guided installer again. This will generate an updated set of manifests that can be deployed using
kubectl apply -f manifest-file.yml.
We do not recommend applying a new version of the manifest file without removing the previous one first, since it might leave some leftover components in your cluster.
To uninstall the Kubernetes integration using Helm, run the following command. Note that
newrelic-bundle is the default release name specified by the guided installer.
$helm uninstall newrelic-bundle -n newrelic
After having installed our Kubernetes integration, you can start instrumenting the services than run in your cluster. To learn more about how to do this, please check our Monitor services running on Kubernetes page.
Learn more about how to: