Find which RoleBinding/ClusterRoleBinding is related to a ServiceAccount kubectl get clusterrolebindings -o json | jq -r ' .items | select( .subjects //  | . | [.kind,.namespace,.name] == ["ServiceAccount","kube-system","node-controller"] ) | .metadata.name' kubectl get clusterrolebindings -o json | jq -r '.items | select(.subjects //  | . | [.name] == ["
"] ) | .metadata.name'
kubectl get rolebindings --all-namespaces -o
There are plenty of articles explains how to debug K8S applications, for example * Troubleshoot Applications [https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/] * Connect with SSH to Azure Kubernetes Service (AKS) cluster nodes for maintenance or troubleshooting [https://docs.microsoft.com/en-us/azure/aks/ssh] Due to the nature of container's
In my previous article Deploy a Ubuntu Based Flannel K8S Cluster in Azure with ARM Template and Kubeadm [https://msazure.club/deploy-a-ubuntu-based-flannel-k8s-cluster-in-azure-with-arm-template-and-kubeadm/] , I provided an Azure ARM template to deploy a flannel networking K8S cluster on Azure. But how flannel networking works, in this article we will discuss a little
The infomation migth be outdated here as acs-engine adds support for Flannel recently with PR 2967 [https://github.com/Azure/acs-engine/pull/2967] However, if you want to gain more control on your kubernetes cluster in Azure, in our case, by using kubeadm, this article still applies. 0. Prerequisites * Azure