Configurar balanceadores de carga HTTP e de rede avaliações

Swetha sri G. · Revisado há 3 days

Parthasarathi B. · Revisado há 3 days

Shubha s. · Revisado há 3 days

Roman M. · Revisado há 3 days

Vinitha S. · Revisado há 3 days

Task 5 needed more explanation

Abdelrahman T. · Revisado há 3 days

Peter F. · Revisado há 3 days

Hamza E. · Revisado há 3 days

Emmanuel O. · Revisado há 3 days

Sarah S. · Revisado há 3 days

Raviteja T. · Revisado há 3 days

Harika K. · Revisado há 3 days

Gunnala S. · Revisado há 3 days

Deepak kumar L. · Revisado há 3 days

Apri K. · Revisado há 3 days

Praveen V. · Revisado há 3 days

Sridhar C. · Revisado há 3 days

5

Vaishnavi P. · Revisado há 3 days

Vaishali S. · Revisado há 3 days

Guru44 G. · Revisado há 3 days

Aman K. · Revisado há 3 days

Bhagya r. · Revisado há 3 days

Lavanya M. · Revisado há 3 days

Rahul K. · Revisado há 3 days

As for me, it will be better to have a deployment diagram in the lab, or smth like that. Maybe that's because I'm not a DevOps but IT PM and it needs more time for me (and constant verification with documentation on gcloud CLI) to understand WHAT I'm currently doing by copying/entering code from the lab and WHY. That's why I would prefer to have: a). target ("to be") diagram on the start of the lab b). current ("as is") diagram on every step, or at least for every task

Anatoliy A. · Revisado há 3 days