If there are problems with the performance of your platform instance, you can use the kubectl get and kubectl logs commands to analyze them.
The kubectl get command allows you to find out the current status of objects in the Kubernetes cluster. For example, this is how you can get the statuses of all the pods:
kubectl get pod --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
app-0 cm-acme-http-solver-2ddt7 0/1 Pending 0 11d
app-0 cm-acme-http-solver-zhgvs 0/1 Pending 0 11d
app-0 create-user-gkgqp 0/1 Completed 0 24d
app-0 deploy-instance-n8j6r 0/1 Completed 0 24d
app-0 extremum-crudl-deployment-7d8cb4f5d8-5cmwd 1/1 Running 0 7d1h
app-0 extremum-iam-deployment-78f5bcf787-wd7qn 1/1 Running 0 16d
app-0 keycloak-deployment-79576dcccc-2482s 1/1 Running 0 50d
app-1 create-user-bvvrg 0/1 Completed 0 55d
app-1 deploy-instance-8g6wb 1/1 Running 0 55d
app-1 extremum-crudl-deployment-9db7bf97b-frpqz 1/1 Running 14837 55d
<... skipped ...>
The kubectl logs command allows you to view the pod log:
kubectl logs coredns-7bc8cf4789-7bnvp -n kube-system --tail 3
2022-09-22T16:34:07.654Z [ERROR] plugin/errors: 2 redis-0.service.dc1.consul. CNAME: read udp 10.112.128.18:57163->10.96.148.224:53: i/o timeout
2022-09-22T16:34:14.569Z [ERROR] plugin/errors: 2 redis-0.service.dc1.consul. A: read udp 10.112.128.18:56822->10.96.148.224:53: i/o timeout
2022-09-22T16:34:14.658Z [ERROR] plugin/errors: 2 redis-0.service.dc1.consul. A: read udp 10.112.128.18:41867->10.96.148.224:53: i/o timeout
Log analysis often helps to understand what exactly led to an abnormal situation. Therefore, journals are a valuable source of information for specialists serving as support Extremum
$ nslookup api.app-0.aje4u4dasmhat70nvns1.y.extremum.io
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find api.app-0.aje4u4dasmhat70nvns1.y.extremum.io: NXDOMAIN
$ nslookup api.app-0.aje4u4dasmhat70nvns1.y.extremum.io
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find api.app-0.aje4u4dasmhat70nvns1.y.extremum.io: NXDOMAIN