Portal overview of Kubernetes services is missing certain fields

[naioja]

What happened: In the Portal view of the Kubernetes Service there's a filed missing stating the status of an AKS cluster started/running or stopped.

What you expected to happen: For Virtual Machine we can have more detailed displayed information as shown below:

How to reproduce it (as minimally and precisely as possible): Just go to the Portal overview of the Kubernetes Services and compare the available fields to the same overview but for Virtual Machines.

[ghost]

Hi naioja, AKS bot here :wave: Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.

I might be just a bot, but I'm told my suggestions are normally quite good, as such: 1) If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster. 2) Please abide by the AKS repo Guidelines and Code of Conduct. 3) If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics? 4) Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS. 5) Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue. 6) If you have a question, do take a look at our AKS FAQ. We place the most common ones there!

[ghost]

Triage required from @Azure/aks-pm

[ghost]

Action required from @Azure/aks-pm

[raghulmsft]

@naioja : Thanks for sharing this! I am a PM with the AKS portal team and will pass it on to see how we can surface additional information like VM does.

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[naioja]

up

[ghost]

Triage required from @Azure/aks-pm

[ghost]

Action required from @Azure/aks-pm

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[shashankbarsin]

@raghulmsft, @chandraneel any updates on this?

[chandraneel]

We added a bunch of fields to the view, and we are not done. We are aware of status being one of the important columns and we are actively working on it. Hopefully will be resolved soon.

[naioja]

@chandraneel looks pretty good !

[ghost]

@jenetlan, @chandraneel, @raghulmsft would you be able to assist?

Issue Details

---

**What happened**: In the Portal view of the Kubernetes Service there's a filed missing stating the status of an AKS cluster started/running or stopped.  **What you expected to happen**: For Virtual Machine we can have more detailed displayed information as shown below:  **How to reproduce it (as minimally and precisely as possible)**: Just go to the Portal overview of the Kubernetes Services and compare the available fields to the same overview but for Virtual Machines.

Author:	naioja
Assignees:	chandraneel, raghulmsft
Labels:	`azure/portal`
Milestone:	-

[ghost]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[naioja]

still an issue

[ghost]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[naioja]

still an issue

[microsoft-github-policy-service[bot]]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.