menu

Using Kubernetes Engine to Deploy Apps with Regional Persistent Disks

Go to Lab

1462 Reviews

In case, the mariadb pvc is created in the same zone as the wordpress pod, the setup can not recover from zone failure, as the mariadb container will be pending with node affinity conflict (missing pvc with standard storage class).

Michael G. · Reviewed sekitar 18 jam ago

Ankit H. · Reviewed sekitar 21 jam ago

Tomasz Z. · Reviewed 1 hari ago

There was an error at the end, after simulating the failure, and the cluster couldn't recover (move the pod and add a node), hence the wordpress app stopped working after the failure. The cluster details show a size of 3 but there was only 2 nodes. The pod restarted 3 times and was showing the status `CrashLoopBackOff`. The version of k8s is `1.14.7-gke.10` and my project id is `qwiklabs-gcp-00-8e3060e0c3e6`

Iheb K. · Reviewed 1 hari ago

Edward F. · Reviewed 2 hari ago

Raul H. · Reviewed 2 hari ago

Bobby R. · Reviewed 2 hari ago

This lab is broken. The mariadb volume is only in one zone, and if that is the zone you kill the instace group in, it is unable to reschedule, and thus even though wordpress was able to move, it won't be able to contact the database.

Rob S. · Reviewed 3 hari ago

Dante Henrique S. · Reviewed 3 hari ago

mariadb was using a standard persistent disk and lost access to its storage...

Bertrand D. · Reviewed 3 hari ago

Anantasak T. · Reviewed 3 hari ago

Sunjith S. · Reviewed 4 hari ago

good

Raju P. · Reviewed 5 hari ago

Thibault H. · Reviewed 5 hari ago

Doesn'r work word press after deleting the instance group

Daeseong K. · Reviewed 6 hari ago

william n. · Reviewed 7 hari ago

Loris S. · Reviewed 7 hari ago

Mariusz K. · Reviewed 7 hari ago

Daniil G. · Reviewed 8 hari ago

Daniil G. · Reviewed 8 hari ago

mohammed B. · Reviewed 8 hari ago

ChangNam G. · Reviewed 8 hari ago

Luiz C. · Reviewed 8 hari ago

Sheng-Yao T. · Reviewed 8 hari ago

Hardik P. · Reviewed 9 hari ago