Managing Deployments Using Kubernetes Engine Reviews

GOOD

Shaumick P. · Reviewed 2 days ago

Janhvi H. · Reviewed 2 days ago

Eric Wijaya Lay C. · Reviewed 2 days ago

Tapasi D. · Reviewed 2 days ago

Disha D. · Reviewed 2 days ago

Abhay G. · Reviewed 2 days ago

Miguel M. · Reviewed 2 days ago

Maximilian L. · Reviewed 2 days ago

Vigneshwaran N. · Reviewed 2 days ago

Ganesh Ram Kumar A. · Reviewed 2 days ago

Iron F. · Reviewed 2 days ago

Wisdom O. · Reviewed 2 days ago

Pranav J. · Reviewed 2 days ago

Srikrishna s. · Reviewed 2 days ago

Michael J. · Reviewed 2 days ago

Md Afjal Q. · Reviewed 2 days ago

Ivan P. · Reviewed 2 days ago

Did it second time and completed it ! 1st lab try, I can't figure out the difference between "paused" and "resumed" deployment status with command "kubectl rollout status deployment/hello". On 2nd try I noticed that pausing deployment will retain some pods with "1.0.0" version and others with "2.0.0" version. So I understand that rolling update starts a pod with next version before stopping one with previous version, and so on... Until next version complétely deployed. Would be great to have a small explanation or schema of the concept :)

Christophe C. · Reviewed 2 days ago

Kumar S. · Reviewed 2 days ago

saleem G. · Reviewed 2 days ago

Danayya M. · Reviewed 2 days ago

Jainish P. · Reviewed 2 days ago

Khushi G. · Reviewed 2 days ago

Alisha K. · Reviewed 2 days ago

Aditya K. · Reviewed 2 days ago