Notes
Follow standard procedures to install or update the New Relic integration for Kubernetes.
Changelog
- Changed: The integration now uses the Infrastructure agent v1.9.0. For more information refer to the Infrastructure agent release notes between versions v1.8.32 and v1.9.0.
Notes
Follow standard procedures to install or update the New Relic integration for Kubernetes.
Changelog
Added: samples for Statefulsets, Daemonsets, Endpoints and Services.
Added: API Server metrics can now be queried using the secure port. Configure the port using the
API_SERVER_SECURE_PORTenvironment variable. The ClusterRole has been updated to allow this query to happen.Changed: The integration now uses the infrastructure agent v1.8.32-bundle. For more information, refer to the Infrastructure agent release notes between versions v1.8.23 and v1.8.32.
The bundle container contains a subset of On-host integrations that are supported by New Relic. This also includes the ability to "Auto Discover" services running on Kubernetes in a similar way to our Container auto-discovery
Changed: The integration has been renamed from
nr-kubernetestonri-kubernetes.
Notes
Follow standard procedures to install or update the New Relic integration for Kubernetes.
Changelog
- Added: Control Plane components can now also be discovered using the
tierandcomponentlabels, besidesk8s-app. You can read more about this in the control plane monitoring section of the docs. - Added: the
newrelic-infra-ctlbinary is now included as part of the image. - Changed: The integration now uses the infrastructure agent v1.8.23. For more information refer to the infrastructure agent release notes between versions v1.5.75 and v1.8.23.
Notes
Follow standard procedures to install the New Relic integration for Kubernetes events.
Changelog
Add custom attributes support. Custom attributes are added via environment variables of the form
NRI_KUBE_EVENTS_<key>=<val>.Example: To add an attribute called
environmentwith a value ofstagingto all the events, you need to add the following environment variable to the spec of thekube-eventscontainer:NRI_KUBE_EVENTS_environment=stagingMore detailed information can be found in the integration's documentation.
Add retry with exponential back-off when sending events to the forwarder agent.
Notes
Follow standard procedures to install or update the New Relic integration for Kubernetes.
Changelog
Added: Control Plane Monitoring: from this release on the Kubernetes integration will automatically monitor your Control Plane, showing each component and their health status in the Kubernetes cluster explorer. Managed Kubernetes Clusters (GKE, EKS, AKS, DO, etc) are not supported, due to technical restrictions.
Added: KSM can now be discovered using custom pod labels. By default we look for pods with the labels
k8s-app,apporapp.kubernetes.io/namewith the valuekube-state-metrics.
If you want to use a custom label for the discovery, you should put the label name in the environment variable namedKUBE_STATE_METRICS_POD_LABEL.If more than 1 pod is found with the label, it will always choose the first one based on a sorted list of IP addresses.
Example:# Label a specific KSM pod. Always set the value to the string "true".kubectl label pod kube-state-metrics newrelic-ksm=trueUpdate the newrelic-infrastructure-k8s manifest to use this labeled KSM pod:
env:- name: KUBE_STATE_METRICS_POD_LABELvalue: newrelic-ksm
Notes
Follow standard procedures to install or update the New Relic integration for Kubernetes.
Changelog
Changed: The integration now uses the Infrastructure agent v1.5.75. For more information, please refer to the Infrastructure agent release notes between versions v1.5.31 and v1.5.75.
Notes
Follow standard procedures to install or update the New Relic integration for Kubernetes.
Changelog
Changed: The integration reverts to the Infrastructure agent v1.5.31, because there were some issues, like clusters not showing in the New Relic entity list UI, caused by use of agent version v1.5.51.
Notes
Follow standard procedures to install or update the New Relic integration for Kubernetes.
Changelog
Added: Node labels are now retrieved from the Kubernetes API and added to the K8sNodeSample. They can now be selected in the Narrow Down Entities section of the infrastructure alerts page to filter entities when using the K8sNodeSample, and can also be used on any NRQL statement when querying the K8sNodeSample. Ex:
FROM K8sNodeSample SELECT average(cpuUsedCoreMilliseconds) WHERE `label.kubernetes.io/role` = 'master'By default, Information retrieved from the Kubernetes API is cached for 5 minutes. The cache time can be changed with the API_SERVER_CACHE_TTL environment variable.
Changed: The integration now uses the Infrastructure Agent v1.5.51. For more information, please refer to the infrastructure agent release notes between versions v1.5.31 and v1.5.51.