New Relic's Kubernetes integration can be installed directly on a server or VM, or through several cloud platforms, such as GKE, EKS, AKS, or OpenShift. Each has a different compatibility with our integration.
If you are using Openshift, you can also use
kubectl most of the time but be careful that
kubectl does not have commands like
oc login or
oc adm. You may need to use
oc instead of
Our Kubernetes is compatible and is continuously tested on the following versions:
1.16 to 1.24
New Relic's Kubernetes integration is compatible with different flavors. We tested the integration with the following ones:
Amazon Elastic Kubernetes Service (EKS)
Amazon Elastic Kubernetes Service Anywhere (EKS-Anywhere)
Amazon Elastic Kubernetes Service on Fargate (EKS-Fargate)
Rancher Kubernetes Engine (RKE1)
Extra configuration is needed to instrument control plane compoenents
Azure Kubernetes Service (AKS)
Google Kubernetes Engine (GKE)
Tested with OpenShift 4.10 and lower. Note that 3.x versions are no longer supported.
Compatible with VMware Tanzu (Pivotal Platform) version 2.5 to 2.11, and Ops Manager version 2.5 to 2.10
Depending on the installation method, the control plane monitoring is not available or may need extra configuration.
- Only API Server metrics are scrapable and available to instrument managed clusters (GKE, EKS, AKS) control plane because no endpoint exposes the needed metrics for etcd, Scheduler and Controller manager.
- To instrument Rancher control plane, since components
/metricsare not always reachable by default and can't be autodiscovered, some extra configuration is needed.
The New Relic Kubernetes integration has the following requirements:
- A New Relic account. Don't have one? Sign up for free. No credit card required.
- Linux distribution compatible with New Relic infrastructure agent.
kube-state-metricsversion 1.9.8 running on the cluster.
- When using CRI-O as the container runtime, the processes inside containers are not reported. Performance data is collected at the container level.
Our Kubernetes integration is CRI-agnostic. It's been specifically tested to be compatible with Containerd, CRI-O, and Docker.
For instructions about how to install our integration using Helm, see Manual install using Helm.