Microsoft releases in GA in December 2020, Kubernetes Resource View.

Kubernetes Resource View

This view gives you the possibility to see:

  • Namespaces on your cluster
  • Workloads to see your deployments, replica, pods, etc.
  • Services and ingresses to check services and ingress deployed on your cluster
  • Storage to check PVC, PV and storage classes
  • Configuration to check secrets and ConfigMap

On each section, you can filter per namespace to have a better view.

The first thing to do to have these views is to activate it by following steps on one of tabs.

After that, you must have the following permissions to be able to view resources:

  • AKS access
  • Kubernetes API (if you have Public IP restriction, your public IP must be allowed, otherwise, you will have an error)
  • Kubernetes objects

As example, we will create/modify/delete namespaces. I created a new namespace, from CLI, named teststarwind:

Сreate/modify/delete namespaces

Let’s delete it by selecting it and clicking on delete. Check the box to be able to click on delete:

Let’s delete it

Namespaces list / teststarwind

From the portal, to create a new namespace, click on Add and paste the following code:

Add with YAML

Namespaces list / portalstarwind

You can edit the yaml, directly from the portal:

Edit the yaml, directly from the portal

VSAN from StarWind is software-defined storage (SDS) solution created with restricted budgets and maximum output in mind. It pulls close to 100% of IOPS from existing hardware, ensures high uptime and fault tolerance starting with just two nodes. StarWind VSAN is hypervisor and hardware agnostic, allowing you to forget about hardware restrictions and crazy expensive physical shared storage.

Build your infrastructure with off-the-shelf hardware, scale however you like, increase return on investment (ROI) and enjoy Enterprise-grade virtualization features and benefits at SMB price today!


So as you can see, if you are not a cmdline specialist, and you need a GUI, this tool will be very helpful for you, but also for your team, to start adopting AKS.

Back to blog