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.
Compatibility
Our Kubernetes integration is compatible with the following versions, depending on the installation mode:
Install mode or feature | Kubernetes versions |
|---|---|
Kubernetes cluster | Currently tested with versions 1.16 to 1.22 |
Kubernetes cluster GKE | Currently tested with versions 1.17 to 1.19 |
Kubernetes cluster EKS, EKS-Anywhere, EKS-Fargate | Compatible with version 1.16 or higher |
Kubernetes cluster AKS | Compatible with version 1.16 or higher |
Kubernetes cluster OpenShift | Currently tested with versions 4.6 |
Kubernetes cluster VMware Tanzu | Compatible with VMware Tanzu (Pivotal Platform) version 2.5 to 2.11, and Ops Manager version 2.5 to 2.10 |
Compatible with version 1.16 or higher | |
Compatible with version 1.16 or higher |
Requirements
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.
Install using Helm
For detailed instructions about how to install our integration using Helm, see Manual install using Helm.