a story of kubelogin mess up my aks setup


Following aks connect instructions to run the following command  

kubelogin convert-kubeconfig -l azurecli

Then after i try to run something like 

 kubectl get deployments --all-namespaces=true

Then i get the following error: 

Error: failed to get token: expected an empty error but received: AzureCLICredential: exit status 1

To resolve this, I had to re-run the entire step (clear your kubeconfig along the way)


az aks get-credentials --resource-group myresourcegroup --name mycluster

and skip the kubelogin step as show above (just continue to do kubectl get pods or something) 






Comments

Post a Comment

Popular posts from this blog

The specified initialization vector (IV) does not match the block size for this algorithm

Image
If you're getting  exception when trying to assigned key to a symmetric key and getting error message below :- The specified initialization vector (IV) does not match the block size for this algorithm And your code probably look like something below :- Then you need to go into debug mode and start looking into the supported size for IV as shown in diagram below :- As you can see, IV is 16 bytes, so you need to provide 16 bytes. The same goes for Key field too, if you're adding anything to it. As long as you provide a valid key size, then we're good and you're code will be ready.
Read more