Kubernetes integration release notesRSS

Notes

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

Changelog

• Added: support for querying Kube State Metrics (KSM) instances behind kube-rbac-proxy. This feature only works when paired with the label-based KSM discovery (see release notes of version 1.11.0 for more information). This adds two new environment variables that allow deeper configuration of the feature:
  • KUBE_STATE_METRICS_SCHEME: Whether the query should use the http or https protocols. Defaults to http and doesn't introduce a breaking change in behavior.
  • KUBE_STATE_METRICS_PORT: The port in which the kube-rbac-proxy instance is listening on. You can confirm this by describing your KSM pod. Defaults to 8080 and doesn't introduce a breaking change in behavior.
• Added: Added 4 new environment variables to explicitly set the control plane component base URLs. These variables can be used for Kubernetes configurations, such as OpenShift, that are different than the defaults defined in the section Discovery of master nodes and control plane components. See the section OpenShift 4.x Configuration for more information.
  • SCHEDULER_ENDPOINT_URL: The base URL of the scheduler pod metrics endpoint. The default is the empty string. In this case, the default configuration will be used.
  • ETCD_ENDPOINT_URL: The base URL of the ETCD pod metrics endpoint. The default is the empty string. In this case, the default configuration will be used.
  • CONTROLLER_MANAGER_ENDPOINT_URL: The base URL of the controller manager pod metrics endpoint. The default is the empty string. In this case, the default configuration will be used.
  • API_SERVER_ENDPOINT_URL: The base URL of the API server pod metrics endpoint. The default is the empty string. In this case, the default configuration will be used.
• Fixed: A bug preventing attributes named like selector.<label_name> from being added to some entries in the K8sServiceSample.
• Changed: The integration now uses newrelic/infrastructure-bundle as the base image. The tag used is for the version 1.2.0. For more information on this image please see the New Relic Infrastructure Bundle releases notes.

Notes

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

Changelog

• Changed: Internal changes in the code without any expected customer impact.

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: daemonsetName field to the K8sDaemonsetSample.

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_PORT environment 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-kubernetes to nri-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 tier and component labels, besides k8s-app. You can read more about this in the control plane monitoring section of the docs.
• Added: the newrelic-infra-ctl binary 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 environment with a value of staging to all the events, you need to add the following environment variable to the spec of the kube-events container:

  NRI_KUBE_EVENTS_environment=staging

  Copy

  More 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, 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

  Copy

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

  env:
  - name: KUBE_STATE_METRICS_POD_LABEL
    value: newrelic-ksm

  Copy

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.