-
Notifications
You must be signed in to change notification settings - Fork 2
What could go wrong?
Azure services is very fast moving, in fact we have updates weekly or even daily. Though we're keeping the documentation and hands-on-lab instruction as soon as we could, there could be times where delayed, which results inconsistency with the UI or even raising issues or error.
You may also check out the Issues and/or Pull request for this labs.
This wiki page captures several issues that we've encountered during this hands-on-lab. We recommend you to check out this wiki when you encountered any errors as the following could provide tips on the resolution:
-
Creating AKS cluster: https://github.com/wely/MCW-Containers-and-DevOps/blob/master/Hands-on%20lab/Before%20the%20HOL%20-%20Containers%20and%20DevOps.md#task-10-create-an-azure-kubernetes-service-cluster It's recommended to disable RBAC in Authentication section when creating AKS cluster in this lab. Enabling it would raise additional complexities / issues on the other steps (such as accessing the dashboard, initiating helm, etc.)
-
Shells or Terminal to access Kubernetes and Azure CLI. In Windows - Though you can use Powershell and cmd line, it's recommended to use Bash on Ubuntu on Windows or Ubuntu (from Microsoft Store apps) as shown here: https://github.com/wely/MCW-Containers-and-DevOps/blob/master/Hands-on%20lab/Before%20the%20HOL%20-%20Containers%20and%20DevOps.md#task-3-install-wsl-bash-on-ubuntu-on-windows
-
Installing Azure CLI https://github.com/wely/MCW-Containers-and-DevOps/blob/master/Hands-on%20lab/Before%20the%20HOL%20-%20Containers%20and%20DevOps.md#task-11-install-azure-cli This step will take pretty long time to install, in my case 20-30 mins.
-
Docker, NodeJS, and NPM https://github.com/wely/MCW-Containers-and-DevOps/blob/master/Hands-on%20lab/Before%20the%20HOL%20-%20Containers%20and%20DevOps.md#task-7-complete-the-build-agent-setup Some folks reported that following these steps somehow can't get docker, nodejs, and npm installed. In that case, i'd recommend you to install separate as per the error instruction such as "sudo apt install docker.io"
-
UI Change in Azure DevOps (used to be VSTS) https://github.com/wely/MCW-Containers-and-DevOps/blob/master/Hands-on%20lab/HOL%20step-by-step%20-%20Containers%20and%20DevOps.md#task-7-push-images-to-azure-container-registry Step: 18 Choose "Use the classic editor to create a pipeline without YAML." to stay consistent on UI on subsequent steps.
-
Tunnel in to Kubernetes cluster https://github.com/wely/MCW-Containers-and-DevOps/blob/master/Hands-on%20lab/HOL%20step-by-step%20-%20Containers%20and%20DevOps.md#task-1-tunnel-into-the-azure-kubernetes-service-cluster If you're having access issues : "warning configmaps is forbidden: User "system:serviceaccount:kube-system:kubernetes-dashboard" cannot list configmaps in the namespace "default" close warning persistentvolumeclaims is forbidden: User "system:serviceaccount:kube-system:kubernetes-dashboard" cannot list persistentvolumeclaims in the namespace "default" close warning secrets is forbidden: User "system:serviceaccount:kube-system:kubernetes-dashboard" cannot list secrets in the namespace "default""
There's possibility that you have rbac enabled. in this case, here's the resolution: If AKS cluster uses RBAC, a ClusterRoleBinding must be created before you can correctly access the dashboard. By default, the Kubernetes dashboard is deployed with minimal read access and displays RBAC access errors. The Kubernetes dashboard does not currently support user-provided credentials to determine the level of access, rather it uses the roles granted to the service account. • Create cluster binding for RBAC-enabled clusters kubectl create clusterrolebinding kubernetes-dashboard --clusterrole=cluster-admin --serviceaccount=kube-system:kubernetes-dashboard Ref: https://github.com/Azure/AKS/issues/601
- If you've encountered issue on NodeJS connnecting to CosmosDB in https://github.com/wely/MCW-Containers-and-DevOps/blob/master/Hands-on%20lab/HOL%20step-by-step%20-%20Containers%20and%20DevOps.md#task-4-initialize-database-with-a-kubernetes-job
- Check carefully on the connection string. By default, the database isn't included in the connection string
- If the password contain character "=", please replace it with "%3D" Ref: https://stackoverflow.com/questions/48425520/error-connecting-to-azure-illegal-character-in-password-with-mongoose-5-0-1-but?rq=1
You're welcome to contribute to this wiki if you encountered an issue and resolution :)