Kubernetes integration release notesRSS

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, app or app.kubernetes.io/name with the value kube-state-metrics.
  If you want to use a custom label for the discovery, you should put the label name in the environment variable named KUBE_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=true

  카피

  Update the newrelic-infrastructure-k8s manifest to use this labeled KSM pod:

  env:
  - name: KUBE_STATE_METRICS_POD_LABEL
    value: 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.

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.31. The biggest changes were major improvements to logging and to the StorageSampler. For more information, please refer to the infrastructure agent release notes between versions v1.3.18 and v1.5.31.

Notes

Follow standard procedures to install or update the New Relic integration for Kubernetes.

Changelog

• Fixed: The Docker image has been rebuilt to fix a regression related to the issue: moby/moby#35443.

Notes

Follow standard procedures to install or update the New Relic integration for Kubernetes.

Changelog

• Added: Support for discovering KSMs when running with the label app.kubernetes.io/name. This should fix problems discovering KSM when deploying recent versions of their Helm chart.

Notes

Follow standard procedures to install or update the New Relic integration for Kubernetes.

Changelog

• Fixed: The Docker image has been rebuilt to fix this issue: moby/moby#35443.

Notes

Follow standard procedures to install or update the New Relic integration for Kubernetes.

Changelog

• Fixed: The unprivileged version of Kubernetes integration was running as root after a restart of the container due to kubernetes/kubernetes#78308.
• Fixed: Autodiscovery cache directory permissions got changed from 644 to 744 in order to let the nri-agent user write inside. This change was necessary to release an unprivileged version of the Kubernetes integration.