Balanceamento de carga do Kubernetes v1.5 avaliações

Nuno O. · Revisado há almost 7 years

Anish B. · Revisado há almost 7 years

Andriy K. · Revisado há almost 7 years

好則 太. · Revisado há almost 7 years

Sandeep M. · Revisado há almost 7 years

Adam B. · Revisado há almost 7 years

David Wardana A. · Revisado há almost 7 years

Vladyslav F. · Revisado há almost 7 years

Deenar T. · Revisado há almost 7 years

Kevork B. · Revisado há almost 7 years

Patrick M. · Revisado há almost 7 years

satisfactory

Mayur R. · Revisado há almost 7 years

Artur I. · Revisado há almost 7 years

Moreno R. · Revisado há almost 7 years

amazing

genta a. · Revisado há almost 7 years

Ashish D. · Revisado há almost 7 years

Arijit C. · Revisado há almost 7 years

Petro O. · Revisado há almost 7 years

Task 6 item1 deploys a singe pod (unlike previously where we specified —replicas=3), we then expose the service. In Task7 'creating the ingress', item 2 says "to wait until all three servers are identified", but there is only one backend as per the deployment? Maybe I misunderstood something but with only one pod in the deployment how does this demonstrate load balancing?

Daniel D. · Revisado há almost 7 years

Arijit C. · Revisado há almost 7 years

Arijit C. · Revisado há almost 7 years

Arijit C. · Revisado há almost 7 years

Francisco Jose G. · Revisado há almost 7 years

Simon V. · Revisado há almost 7 years