Continuous Delivery with Jenkins in Kubernetes EngineGo to Lab
there were some unclear/incomplete instructions when doing the jenkins and helm setup.
Quite complex without explanation. Many new concepts, like accessing the jenkins ui via console web preview. Kubectl proxy. How branch canary tiggers canary deployment is not explained. I only managed to find out based on the Jenkinsfile
Very complex and only coders can able to perform this without confusion for architects its really a night mare to understand the whole steps to configure it