Managed Kubernetes cluster monitoring and logs

Last update: March 04 2024

Managed Kubernetes cluster monitoring and logs

In Managed Kubernetes clusters, you can monitor the state of the cluster — see cluster status and logs.

View cluster status⁠

1. In Control Panel, go to Cloud Platform → Kubernetes.
2. View the status in the cluster row → Status column.

ACTIVE	Cluster is available
PENDING_CREATE	Cluster is created
PENDING_ROTATE_CERTS	Updates certificates and keys for Kubernetes Control Plane
PENDING_NODE_REINSTALL	One of the nodes is reinstalled
PENDING_UPDATE_NODEGROUP	Node group settings are updated
PENDING_UPGRADE_PATCH_VERSION	Cluster is updated to new patchversion
PENDING_UPGRADE_MINOR_VERSION	Cluster is updated to new minor version
PENDING_UPGRADE_MASTERS_CONFIGURATION	Cluster master nodes are serviced
PENDING_UPGRADE_CLUSTER_CONFIGURATION	Cluster master nodes are serviced and then reset.cluster master nodes are being serviced and then restarted
PENDING_RESIZE	Cluster is scaling
MAINTENANCE	Cluster is in maintenance mode, any scaling is unavailable
ERROR	An error occurred. Open the cluster page → tab Logs → event row → column Status. If the cause of the error is insufficient quotas in the project, increase quotas . If no reason is specified, create a ticket
PENDING_DELETE	Cluster is deleted

View logs⁠

The logs show actions performed on the cluster, such as creating the cluster, changing node groups, updating certificates and versions. If the request was performed automatically, for example, a scheduled certificate update, this action will also be logged.

1. In Control Panel, go to Cloud Platform → Kubernetes.
2. Open the cluster page → Logs tab.
3. Look up the status in the event row → Status column.

Configure logging via Filebeat⁠

Containers log files are located in /var/log/pods/ or /var/log/containers (link to /var/log/pods/).

Filebeat is configured to work with Docker by default. Selectel uses containerd as the container execution environment (CRI) instead of Docker.

To configure the mechanism for retrieving log metadata via Filebeat, use the configuration file:

filebeat.inputs:
- type: container
  fields_under_root: true
  paths:
  - "/var/log/containers/*.log"
  processors:
    - add_kubernetes_metadata:
        host: ${NODE_NAME}
        in_cluster: true
        default_matchers.enabled: false
        matchers:
        - logs_path:
            logs_path: "/var/log/containers/"