Kubernetes service status

Question

Kubernetes service status

Sai Theja 21

I have performed a restart on cluster level,

But the pods came up and underlying apps are running, but when i try to autoscale the machines by deleting, pods are not responding and error is throwing as server is not available.

Status is on starting(running) instead of succeeded(running).

taking longer time than usual restart.

Kindly help on it.

KarishmaTiwari-MSFT 20,822 Reputation points Microsoft Employee Moderator

2022-09-03T02:56:33.737+00:00

@Sai Theja
Are you still seeing this issue? Please let us know.

There was an Azure outage on Aug 30th that might have caused this issue. It is mitigated.
Sai Theja 21 Reputation points

2022-09-04T02:55:29.71+00:00

Hi @KarishmaTiwari-MSFT

We have tried cluster restart on the particular day and it resolved but took too long for restarting.

Now haven't verified yet, will let you if i face same issue.

Currently everything is fine and running as expected.

1 answer

Your answer

KarishmaTiwari-MSFT 20,822 Reputation points Microsoft Employee Moderator

2022-09-03T02:56:33.737+00:00

@Sai Theja
Are you still seeing this issue? Please let us know.

There was an Azure outage on Aug 30th that might have caused this issue. It is mitigated.
Sai Theja 21 Reputation points

2022-09-04T02:55:29.71+00:00

Hi @KarishmaTiwari-MSFT

We have tried cluster restart on the particular day and it resolved but took too long for restarting.

Now haven't verified yet, will let you if i face same issue.

Currently everything is fine and running as expected.

Answer 1

Nadav Ben Haim 501 Microsoft Employee

Hello,
do you have access to the cluster via kubectl?
If the cluster has a large amount of nodes and workloads it will take sometime for it to start.
if you do have access via kubectl and the cluster is in Starting,
please check if all nodes are up by using :

kubectl get nodes -o wide

Let me know

Sai Theja 21 Reputation points

2022-08-31T12:43:02.727+00:00

Hi @Nadav Ben Haim ,

Thanks for the reply, i have verified all pods are up and running, checked nodes as well.

But it took too long to start and change to succeeded state. Later pods are responsive.

This is because we tried to run the pods by deleting one of it. but they are not running but in the state of imagepulloff not aware on what to do so proceeded to

restart via cluster. Pods are still in the same state as container creating.

help me on this state. how to proceed further.

this procedure of restart of via cluster is taking too long to start.
Nadav Ben Haim 501 Reputation points Microsoft Employee

2022-08-31T13:19:12.147+00:00

Can you specify which pods are stuck in that state?
Or show one of them by using kubectl describe [podname]?
Sai Theja 21 Reputation points

2022-08-31T17:08:52.783+00:00

I have attached screenshot, tried to delete pod but as per HA pods should create and run,

Yet pods are staying in same state.
Sai Theja 21 Reputation points

2022-09-04T02:52:33.523+00:00

Hi @Nadav Ben Haim

Have you got time to verify it.

Please help me on this issue.
Nadav Ben Haim 501 Reputation points Microsoft Employee

2022-09-05T15:38:02.99+00:00

Are all of these container images being pulled from the same ACR?

Share via

Kubernetes service status

1 answer

Your answer