--- title: Kubernetes summary page source: https://docs.newrelic.com/docs/apm/apm-ui-pages/monitoring/kubernetes-summary-page --- The Kubernetes APM **summary** page provides general information about the selected application, including the age of the current workload, the number of pods available, CPU and memory usage, pod logs, and metric comparison. ![This is an image of the Kubernetes APM page](https://docs.newrelic.com/images/apm_screenshot-crop_k8-apm-ui-workload.webp "Kubernetes page") Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > APM & Services > (selected app) > Kubernetes** > #### 💡 TIP > > To get a high-level overview of all your applications and services, use our [entity explorer](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/core-concepts/new-relic-explorer-view-performance-across-apps-services-hosts/). ## Monitor the deployment of your Kubernetes cluster [#monitor-kubernetes] The Kubernetes page in APM offers the following information about your application: **Workload summary** You can see your workload's name, type, cluster, and namespace at the top of the page. ![This is an image of the Kubernetes APM page workload header](https://docs.newrelic.com/images/apm_screenshot-crop_k8-workload-header.webp "Kubernetes page - Workload header") If your app has multiple workloads (for example, it spans multiple clusters, or it includes several **Deployment**, **StatefulSet**, **DaemonSet**, or **ReplicaSet** resources), the **Kubernetes** page shows you a table listing every workload, with columns for **Workload**, **Type**, **Namespace**, **Cluster**, **Pods** (available, desired, and missing), and **Containers**. Click **View** on a row to drill into that workload, or click **Back to all workloads** to return to the table. ![This is an image of the Kubernetes APM page workload table](https://docs.newrelic.com/images/apm_screenshot-crop_k9-multi-workload.webp "Kubernetes page - Workload table") A workload's cluster can belong to a different New Relic account than the APM app it's linked to. The table only shows the clusters and workloads that you already have access to. **Current workload** You can check how many pods are available or desired, the pods that are missing, and the age of the workload, which is the date when it was first created. ![This is an image of the Kubernetes APM page](https://docs.newrelic.com/images/apm_screenshot-crop_k8-current-workload.webp "Kubernetes page - Current workload") **Performance summary for the workload** You can see the CPU and memory utilization, as well as the number of pod restarts. ![This is an image of the Kubernetes APM page](https://docs.newrelic.com/images/apm_screenshot-crop_k8-performance.webp "Kubernetes page - Performance summary") **Pods and containers** You can check pod and their related containers details. If you click the pod or container name, you'll get some details about it in a slide-out panel. In addition, with the **Logs** button, you can see the logs in context to that pod. ![This is an image of the Kubernetes APM page](https://docs.newrelic.com/images/apm_screenshot-crop_k8-pods-containers-table.webp "Kubernetes page - Pods and Containers") **Activity stream** You can see the stream of Kubernetes events related to that deployment and its pods. ![This is an image of the Kubernetes APM page](https://docs.newrelic.com/images/apm_screenshot-crop_k8-activity-stream.webp "Kubernetes page - Activity stream") **Metrics comparison** These widgets let you compare a static list of metrics related to the pods-containers in the deployment, as well as other metrics such as CPU, network, storage. ![This is an image of the Kubernetes APM page](https://docs.newrelic.com/images/apm_screenshot-crop_k8-metric-comparasin.webp "Kubernetes page - Metrics Comparison") The following metrics are available: - CPU usage (cores) - CPU throttling (%) - Memory usage (bytes) - Network received (KBps) - Network transmitted (KBps) - Network errors (per second) - Storage usage (bytes) - Storage utilization (%) - Container restart count - Service throughtput (requests per minute) - Service response time (ms) - Service error rate (%) ## Link your applications to Kubernetes [#link-app] You can surface Kubernetes metadata and link it to your APM agents, whether you use our proprietary agents or OpenTelemetry. APM uses the Kubernetes metadata to display the specific Kubernetes deployment information related to that APM application. ### New Relic proprietary instrumentation [#nr-proprietary] When you [install New Relic's Kubernetes integration](/install/kubernetes/), New Relic's metadata injection comes into play automatically via the `nri-metadata-injection` parameter. The `MutatingAdmissionWebhook`, set up by the Kubernetes instrumentation, takes care of tagging your pods with the necessary environment variables. From there, the data captured in these variables gets carried over to your APM metrics and entities, enriching them with valuable context. For more information, see how to [link your applications to Kubernetes](https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-your-applications-kubernetes/). The following attributes are required in the APM service entity to display the Kubernetes summary page: - `k8s.clusterName` - `k8s.namespaceName` - `k8s.deploymentName` ### OpenTelemetry instrumentation [#otel-instrumentation] The [OpenTelemetry Collector](https://docs.newrelic.com/docs/opentelemetry/get-started/collector-processing/opentelemetry-collector-processing-intro/) offers a Kubernetes attributes processor that enrich APM telemetry with Kubernetes metadata. 1. You need to define an environment variable in your deployment manifest. 2. Adjust the configuration of the Collector to retrieve the appropriate Kubernetes metadata using this APM environment variable. As a result, all the APM metrics and entities will include Kubernetes metadata thanks to the `K8sattributes` processor. For more information, see how to [link your OpenTelemetry applications to Kubernetes](https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-otel-applications-kubernetes/). The following attributes are required in the APM service entity to display the Kubernetes summary page: - `k8s.cluster.name` - `k8s.deployment.name` - `k8s.namespace.name` > #### ⚠️ IMPORTANT > > The Kubernetes summary page works with a mix of instrumentation providers (New Relic and OpenTelemetry). However, if Kubernetes is monitored by OpenTelemetry agents and APM is monitored by New Relic agents, install nri-metadata-injection to ensure it works properly by providing the necessary Kubernetes metadata to the APM metrics.