gke - service mesh installation failed

Got this weird error message here:-


And you need to check by running the following command 

kubectl describe controlplanerevision -n istio-system

Looking at the type = reconciled that means that's good. 



Amd then when i run istio samples helloworld.yaml, these pods are created with istio side car



References 

https://cloud.google.com/service-mesh/docs/troubleshooting/troubleshoot-ui-onboarding?authuser=1&hl=en&_gl=1*4d0rwh*_ga*MTgzNzIzNDc4NC4xNzM2MjY5NjQ1*_ga_WH2QY8WWF5*MTc0MjkxNjM0Ny42Ni4xLjE3NDI5MTk3NjQuNTEuMC4w




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

NodeJS: Error: spawn EINVAL in window for node version 20.20 and 18.20

Encounter this issue when running autorest (that uses nodejs).  I am using node version:  v18.20.2 After i revert to use node v18.12.0, then i was able to get my app to run without this error. Since i am working with Azure devops yaml, i was able to use the following to resolve my issue.  - task : NodeTool@0   inputs :     versionSource : 'spec'     versionSpec : '18.18.0'
Read more