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.
Looking to install our New Relic One integration with Pixie for fine-grained telemetry data? See our Auto-telemetry with Pixie install instructions to get deeper insight into your Kubernetes clusters and workloads with just one install command. No language agents required.
Want to try out our Kubernetes integration? Create a New Relic account for free! No credit card required.
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 do not wish 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.
Alternatively, we also offer fully 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 integraiton 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 comapred to using manifests directly.
If custom manifests have been used instead of Helm, we encourage you to first remove the old installation using
kubectl delete -f <mark>previous-manifest-file.yml</mark>, and then proceed through the guided installer again. This will generate an updated set of manifests that can be deployed using
kubectl apply -f <mark>manifest-file.yml</mark>.
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.
We encourage you to deploy our integration using Helm, as it allows easier configuration on how to monitor services by just adding snippets to your
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.
To learn more about how to use your Kubernetes data, please head to our detailed Find and use your Kubernetes data pages.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.