Display status information for Deployments in Application Explorer tree #3823

[vrubezhny]

Fixes: #3823

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 33.84615% with 43 lines in your changes are missing coverage. Please review.

Project coverage is 44.00%. Comparing base (da60441) to head (7e7dbed).
Report is 260 commits behind head on main.

Files	Patch %	Lines
src/explorer.ts	33.84%	43 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #4148       +/-   ##
===========================================
+ Coverage   32.37%   44.00%   +11.62%     
===========================================
  Files          85       91        +6     
  Lines        6505     7352      +847     
  Branches     1349     1567      +218     
===========================================
+ Hits         2106     3235     +1129     
+ Misses       4399     4117      -282     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vrubezhny]

At the moment the Deployment info looks like this:

The Pod Container Failures part is the failures obtained from the Pod containers - where we're looking for the CrashLoopBackOff state. We can skip these at all or show only for those containers that permanent in CrashLoopBackOff state, so we could know the reason of that state.

[vrubezhny]

With the latest PR update we show:

• Deployment name,
• Number of Available Replicas,
• Actual number of created Replicas,
• Detected CrashLoopBackOff state,
• Pod Container Failures (if any)
• Deployment Failures (if any)

The Deployment element icon has:

• Green modifier when all the Pods are successfully started and running,
• Yellow modifier when no CrashLoopBackOff state is detected, but not all the Pods are successfully started and running
• Red modified when either CrashLoopBackOff state is detected or at least one of the pods has Failed or Unknown state

[datho7561]

Overall working great! Saw a few things in the code. I haven't been able to get the yellow status to show up, but it might be because it would only show up very briefly as we discussed.

(sorry it took so long to get to this).

[vrubezhny]

I haven't been able to get the yellow status to show up, but it might be because it would only show up very briefly as we discussed.

That's simple: Just deploy your pet-alpine image to the Sandbox cluster - we've already discussed this - the CrashLoopBackOff doesn't appear on Sandbox because the Pod cannot be created, the CreateContainerError is reported instead and the Pod is reported as Pending. So it makes it "yellow".

PS: Probably I was wrong... After working a few hours the pet-alpine deployment got "red" with CrashLoopBackOff, so it's stays yellow for a limited time on Sandbox.

[datho7561]

Looks good to me. Very informative of the deployment's state. Thanks, Victor!