Skip to content

Latest commit

 

History

History
217 lines (142 loc) · 4.54 KB

MAINTENANCE.md

File metadata and controls

217 lines (142 loc) · 4.54 KB
Raw

Maintenance

Verification of service state

This part of the documentations covers the topic how to check if each component is working properly.

- Kubernetes

Verify status of Kubernetes kubelet service with the command:

systemctl status kubelet
- kubectl

Check state of Kubernetes nodes using the kubectl command:

root@primary01:~# kubectl get nodes --kubeconfig=/etc/kubernetes/admin.conf
NAME                                         STATUS   ROLES                  AGE   VERSION
primary01                                    Ready    control-plane,master   23h   vx.xx.x
node01                                       Ready    <none>                 23h   vx.xx.x
node02                                       Ready    <none>                 23h   vx.xx.x

Get additional information about Kubernetes components:

root@primary01:~# kubectl cluster-info --kubeconfig=/etc/kubernetes/admin.conf
Kubernetes control plane is running at https://primary01:6443
CoreDNS is running at https://primary01:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

Check status of pods in all namespaces using the command:

kubectl get pods -A --kubeconfig=/etc/kubernetes/admin.conf

For more detailed information please refer to the official documentation.

- crictl

Check state of Kubernetes components using the crictl command:

List all pods:

crictl pods

List all images:

crictl images

List all containers:

crictl ps -a

The crictl tool provides the possibility to run a sandbox container which may be useful for debugging purposes. For more information, refer to the official documentation.

- Keycloak

To check the if a Keycloak service deployed on Kubernetes is running with the command:

kubectl get pods --kubeconfig=/etc/kubernetes/admin.conf --namespace=keycloak --field-selector=status.phase=Running | grep keycloak

- HAProxy

To check status of HAProxy, use the command:

systemctl status haproxy

Additionally, you can check if the application is listening on ports defined in the file haproxy.cfg running netstat command.

- Prometheus

To check status of Prometheus, use the command:

systemctl status prometheus

Check if Prometheus service is listening at the port 9090:

netstat -antup | grep 9090

- Grafana

To check status of Grafana, use the command:

systemctl status grafana-server

Check if Grafana service is listening at the port 3000:

netstat -antup | grep 3000

- Prometheus Node Exporter

To check status of Node Exporter, use the command:

status prometheus-node-exporter

- OpenSearch

To check the status of OpenSearch we can use the command:

systemct status opensearch

Check if service is listening on 9200 (API communication port):

netstat -antup | grep 9200

Check if service is listening on 9300 (nodes communication port):

netstat -antup | grep 9300

We can also check the status of OpenSearch cluster:

<IP>:9200/_cluster/health

You can do this using curl or any other equivalent tool.

- Kibana

To check status of Kibana, use the command:

systemctl status kibana

Check if Kibana service is listening at the port 5601:

netstat -antup | grep 5601

- Filebeat

To check status of Filebeat, use the command:

systemctl status filebeat

- PostgreSQL

To check status of PostgreSQL, use commands:

  • on Ubuntu:
systemctl status postgresql
  • on Red Hat:
systemctl status postgresql-10

where postgresql-10 is only an example, because the number differs from version to version. Please refer to your version number in case of using this command.

Check if PostgreSQL service is listening at the port 5432:

netstat -antup | grep 5432

Use the pg_isready command, to get information if the PostgreSQL server is running and accepting connections with command:

  • on Ubuntu:
[user@postgres01 ~]$ pg_isready
/var/run/postgresql:5432 - accepting connections
  • on Red Hat:
[user@postgres01 ~]$ /usr/pgsql-10/bin/pg_isready
/var/run/postgresql:5432 - accepting connections

where the path /usr/pgsql-10/bin/pg_isready is only an example, because the number differs from version to version. Please refer to your version number in case of using this command.