menu

Como usar o Kubernetes Engine para implantar aplicativos com discos permanentes regionais

Go to Lab

1605 Revisar

Mohammed Ishaque I. · Avaliado aproximadamente 2 horas atrás

Xiaoping C. · Avaliado aproximadamente 9 horas atrás

best lab so far. tks

Renato T. · Avaliado aproximadamente 14 horas atrás

Abdijabar K. · Avaliado aproximadamente 16 horas atrás

Murali M. · Avaliado 2 dias atrás

Ian R. · Avaliado 2 dias atrás

Dheeraj B. · Avaliado 2 dias atrás

Valerii S. · Avaliado 3 dias atrás

Eugene C. · Avaliado 4 dias atrás

Eugene C. · Avaliado 4 dias atrás

silivanxay p. · Avaliado 5 dias atrás

Moises M. · Avaliado 5 dias atrás

Ryan P. · Avaliado 7 dias atrás

Henri H. · Avaliado 8 dias atrás

Joan G. · Avaliado 8 dias atrás

Felipe G. · Avaliado 8 dias atrás

kamolsit m. · Avaliado 9 dias atrás

Prakash P. · Avaliado 9 dias atrás

Makoto M. · Avaliado 9 dias atrás

nice

Bedilbek K. · Avaliado 9 dias atrás

zone failure simulation didnot work. WP was not reachable. on calling "kubectl get pods -l app=wp-repd-wordpress -o wide" the result was NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES wp-repd-wordpress-694467d7c4-kc7mv 0/1 Running 1 2m52s 10.20.1.6 gke-repd-default-pool-9bd7e7b5-kx3c <none> <none>

Maria B. · Avaliado 9 dias atrás

Memis C. · Avaliado 10 dias atrás

Was unable to view new Wordpress page after simulated failure. The Status was running but 0/1 in the Ready state with 0 Restarts. It continued to echo out the same IP of the one that was deleted. Tried looking into it and it appeared to be an issue with the MariaDB node. In wp-repd-mariadb-0 Pod Details "0/2 nodes are available: 2 node(s) had volume node affinity conflict." Fairly certain I did all the steps (although mistakes are always possible).

Seamus D. · Avaliado 10 dias atrás

Michael R. · Avaliado 11 dias atrás

Sumit P. · Avaliado 12 dias atrás