українська мова ▾ English Deutsch Español Français Português (Brasil) Русский українська мова 简体中文 Topics ▾ Setup and...

Skip to main content Back to top Ctrl + K Plot types User guide Tutorials Examples Reference Contribute Releases Gitt...

Skip to main content Back to top Ctrl + K Plot types User guide Tutorials Examples Reference Contribute Releases Gitt...

Português (Brasil) ▾ English Deutsch Español Français Português (Brasil) Русский українська мова 简体中文 Topics ▾ Setup ...

English ▾ English Deutsch Español Français Português (Brasil) Русский українська мова 简体中文 Topics ▾ Setup and Config ...

English ▾ English Deutsch Español Français Português (Brasil) Русский українська мова 简体中文 Topics ▾ Setup and Config ...

This documentation is about investigating and diagnosing kubectl related issues. If you encounter issues accessing kubectl or connecting to your cluster, this document outlines various common scenarios and potential solutions to help identify and address the likely cause. Before you begin You need to have a Kubernetes cluster. You also need to have kubectl installed - see install tools Verify kubectl setup Make sure you have installed and configured kubectl correctly on your local machine.

To scale an application and provide a reliable service, you need to understand how the application behaves when it is deployed. You can examine application performance in a Kubernetes cluster by examining the containers, pods, services, and the characteristics of the overall cluster. Kubernetes provides detailed information about an application's resource usage at each of these levels. This information allows you to evaluate your application's performance and where bottlenecks can be removed to improve overall performance.

Skip to main content Back to top Ctrl + K Plot types User guide Tutorials Examples Reference Contribute Releases Gitt...

This page shows how to write and read a Container termination message. Termination messages provide a way for containers to write information about fatal events to a location where it can be easily retrieved and surfaced by tools like dashboards and monitoring software. In most cases, information that you put in a termination message should also be written to the general Kubernetes logs. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster.