This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 54%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
I created the AKS using AKS-Engine, from Client - WSL/Ubuntu.
From Client side - i see that pods (and other resources) are running on AKS, but when looking at Azure Home/Monitoring/Containers - it's empty (no any contained).
Below are logs (including AKS creation/deploy command)
At my client:
valerym@DESKTOP-1G5SDPG:~$ k get pod -owide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
nginx-ingress-ingress-nginx-controller-76cd47bb89-28hzp 1/1 Running 0 4d22h 10.240.0.19 k8s-agentpool1-39780674-vmss000000 <none> <none>
nginx-ingress-ingress-nginx-controller-76cd47bb89-ffpf2 1/1 Running 0 4d22h 10.240.0.22 k8s-agentpool1-39780674-vmss000000 <none> <none>
service-a-8b4b57678-777hf 1/1 Running 0 133m 10.240.0.18 k8s-agentpool1-39780674-vmss000000 <none> <none>
service-b-8b48699d6-sbf8z 1/1 Running 0 2d15h 10.240.0.26 k8s-agentpool1-39780674-vmss000000 <none> <none>
valerym@DESKTOP-1G5SDPG:~$
valerym@DESKTOP-1G5SDPG:~$ k get svc -owide
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
my-service-a LoadBalancer 10.0.75.186 <pending> 80:31570/TCP 3d app=service-a
nginx-ingress-ingress-nginx-controller LoadBalancer 10.0.208.34 <pending> 80:30484/TCP,443:31094/TCP 4d22h app.kubernetes.io/component=controller,app.kubernetes.io/instance=nginx-ingress,app.kubernetes.io/name=ingress-nginx
nginx-ingress-ingress-nginx-controller-admission ClusterIP 10.0.226.34 <none> 443/TCP 4d22h app.kubernetes.io/component=controller,app.kubernetes.io/instance=nginx-ingress,app.kubernetes.io/name=ingress-nginx
service-a ClusterIP 10.0.213.75 <none> 8080/TCP,8081/TCP 2d14h app=service-a
service-b ClusterIP 10.0.7.227 <none> 80/TCP 2d15h app=service-b
=============
AKS creation/deploy command I used:
valerym@DESKTOP-1G5SDPG:~/Valera/MicrosoftTask/02_Azure$ aks-engine deploy --subscription-id xxxxx-xxx-xxx-xxxxxx --dns-prefix cloud-shell-storage-westeurope --resource-group cloud-shell-storage-westeurope --location westeurope --api-model kubernetes.json --client-id 630c39b3-70ff-476f-a699-195b9591ff8d --client-secret 8ZsTAh7.aueCNRN_v5Gr7r8RNdlZWzoTZB --set servicePrincipalProfile.clientId="630c39b3-70ff-476f-a699-195b9591ff8d" --set servicePrincipalProfile.secret="630c39b3-70ff-476f-a699-195b9591ff8d"
INFO[0000] new API model file has been generated during merge: /tmp/mergedApiModel975093119
WARN[0003] apimodel: missing masterProfile.dnsPrefix will use "cloud-shell-storage-westeurope"
WARN[0006] containerd will be upgraded to version 1.3.7
INFO[0029] Starting ARM Deployment cloud-shell-storage-westeurope-62492111 in resource group cloud-shell-storage-westeurope. This will take some time...
INFO[0288] Finished ARM Deployment (cloud-shell-storage-westeurope-62492111). Succeeded
valerym@DESKTOP-1G5SDPG:~/Valera/MicrosoftTask/02_Azure$
@Valery Mogilevsky Azure Monitor for containers provides rich monitoring experience for the Azure Kubernetes Service (AKS) and AKS Engine on Azure, which is a self-managed Kubernetes cluster hosted on Azure.
Did you got a chance to enable monitoring of Kubernetes clusters hosted outside of Azure as mentioned here.
The mentioned article is a part of deploying AKS using AKS engine and you might need to setup monitoring to get data on portal side.
Hope it helps!!!
Please 'Accept as answer' if it helped, so that it can help others in the community looking for help on similar topics
Hello @prmanhas-MSFT . Thank you very much for your reply.
My Kubernetes cluster is Not Outside of Azure.
It's in Azure.
It just created from outside, with AKS-Engine. Kubernetes VM created, and is located in Azure.
Suppose it should be handled and displayed by Azure same was as Kubernetes cluster that created inside Azure using UI.
@Valery Mogilevsky Thank you for the clarification :)
Let me reach out to our Product Group on this and I will keep you posted on same.
Thank you for your patience over the matter
@Valery Mogilevsky Thank you for your patience over the matter.
I reached out to our internal team and below is their response:
AKS engine created clusters don’t show up on the Azure Portal as managed (AKS) clusters.
For managed AKS clusters, you would need to deploy AKS clusters as mentioned below:
https://learn.microsoft.com/en-us/azure/aks/
On the other side, if you want to stick with “AKS engine” but would like to see it on the Azure Portal as a Kubernetes clusters, you could consider using Azure Arc for Kubernetes:
https://learn.microsoft.com/en-us/azure/azure-arc/kubernetes/overview
For AKS engine” page below article might be helpful:
https://github.com/Azure/aks-engine for “AKS engine” related topics.
If the suggested response helped you resolve your issue, do click on "Mark as Answer" and "Up-Vote" for the answer that helped you for benefit of the community.
Hello @prmanhas-MSFT . Thank you very much for your kind support and help.
I will try to do all as you sent. Hope will help : )
@Valery Mogilevsky Sure do let me know in case of any queries :)
Thank you @prmanhas-MSFT . Could you please look also on my another question (small hope)
https://learn.microsoft.com/en-us/answers/questions/130809/can39t-connect-azure-vm-created-with-aks-engine-fr.html
@Valery Mogilevsky Sure I will take care of it :)