Managing Deployments Using Kubernetes Engine Reviews

Yachcharesh S S. · Reviewed 12 days ago

Harsh K. · Reviewed 12 days ago

Gautam kumar y. · Reviewed 12 days ago

Sarthak R. · Reviewed 12 days ago

selesai

MKhoiruz G. · Reviewed 12 days ago

Moch. Febri K. · Reviewed 12 days ago

Inggrid C. · Reviewed 12 days ago

Czarrio W. · Reviewed 12 days ago

good

Dhanesh F. · Reviewed 12 days ago

good

Yusuf A. · Reviewed 12 days ago

Satyam G. · Reviewed 12 days ago

Bathula A. · Reviewed 12 days ago

bad

Alfina N. · Reviewed 12 days ago

Teguh A. · Reviewed 12 days ago

Good

Moh Roby Trio D. · Reviewed 12 days ago

Bisakh p. · Reviewed 12 days ago

Preethi P. · Reviewed 12 days ago

Arnol M. · Reviewed 12 days ago

FRANCISCO ISRAEL M. · Reviewed 12 days ago

susah:( bagian edit

Suwito W. · Reviewed 12 days ago

Fitria R. · Reviewed 12 days ago

Super poco intuitivo

Juan R. · Reviewed 12 days ago

Rakshit G. · Reviewed 12 days ago

AMARA SOUJANYA G. · Reviewed 12 days ago

The lab introduction uses the term "Continuous Deployment" as a specific deployment scenario, which is confusing. CD vs. Rolling Update: Academically, Continuous Deployment is a broad methodology, while the technical strategy used here is "Rolling Update". Strategy vs. Scenario: According to the official Kubernetes API, the correct term is "Strategy" (as used in spec.strategy.type), not "Scenario." I suggest updating the terminology to match the official Kubernetes documentation to avoid confusion for students preparing for CKA or GCP certifications.

Rostislav R. · Reviewed 12 days ago