Continuous Delivery with Jenkins in Kubernetes EngineGo to Lab
Time schedule is very very tight. Maybe suggest what should be covered before starting the Lab. Give more time for Lab - builds take time...
Needed about another five minutes, production deployment hadn't finished yet. This one was fairly complex, could have used a little more explanation of what I was executing.
There is no enough time to complete this LAB. It takes so much time to setup features such as load balancer external IP address, and there is also mistakes in the procedure such as the space before jsonpath in the export to the environment variable !!!
Barely enough time to compete due to cluster and load balancer taking nearly 15 minutes to complete each. syntax errors in command took time to debug. Jenkins screens in lab do not match the current Jenkins UI.
Great lab but a few bugs in the code (done missing in one bash script) and tight timeline. Also, very little time/explanation how the jenkins pipeline is configured though I see that this is not part of the curriculum here.