Managing Deployments Using Kubernetes Engine Reviews

Mohamed Shaleel.V.C V. · Reviewed about 1 month ago

Vladimir S. · Reviewed about 1 month ago

Vishal G. · Reviewed about 1 month ago

Ektaa R. · Reviewed about 1 month ago

Waldemar S. · Reviewed about 1 month ago

Mohammed S. · Reviewed about 1 month ago

GOOD

Shaumick P. · Reviewed about 1 month ago

Janhvi H. · Reviewed about 1 month ago

Eric Wijaya Lay C. · Reviewed about 1 month ago

Tapasi D. · Reviewed about 1 month ago

Disha D. · Reviewed about 1 month ago

Abhay G. · Reviewed about 1 month ago

Miguel M. · Reviewed about 1 month ago

Maximilian L. · Reviewed about 1 month ago

Vigneshwaran N. · Reviewed about 1 month ago

Ganesh Ram Kumar A. · Reviewed about 1 month ago

Iron F. · Reviewed about 1 month ago

Wisdom O. · Reviewed about 1 month ago

Pranav J. · Reviewed about 1 month ago

Srikrishna s. · Reviewed about 1 month ago

Michael J. · Reviewed about 1 month ago

Md Afjal Q. · Reviewed about 1 month ago

Ivan P. · Reviewed about 1 month 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 about 1 month ago

Kumar S. · Reviewed about 1 month ago