关于“使用 Kubernetes Engine 管理部署”的评价

Mohamed Shaleel.V.C V. · 已于 about 1 month前审核

Vladimir S. · 已于 about 1 month前审核

Vishal G. · 已于 about 1 month前审核

Ektaa R. · 已于 about 1 month前审核

Waldemar S. · 已于 about 1 month前审核

Mohammed S. · 已于 about 1 month前审核

GOOD

Shaumick P. · 已于 about 1 month前审核

Janhvi H. · 已于 about 1 month前审核

Eric Wijaya Lay C. · 已于 about 1 month前审核

Tapasi D. · 已于 about 1 month前审核

Disha D. · 已于 about 1 month前审核

Abhay G. · 已于 about 1 month前审核

Miguel M. · 已于 about 1 month前审核

Maximilian L. · 已于 about 1 month前审核

Vigneshwaran N. · 已于 about 1 month前审核

Ganesh Ram Kumar A. · 已于 about 1 month前审核

Iron F. · 已于 about 1 month前审核

Wisdom O. · 已于 about 1 month前审核

Pranav J. · 已于 about 1 month前审核

Srikrishna s. · 已于 about 1 month前审核

Michael J. · 已于 about 1 month前审核

Md Afjal Q. · 已于 about 1 month前审核

Ivan P. · 已于 about 1 month前审核

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. · 已于 about 1 month前审核

Kumar S. · 已于 about 1 month前审核