Distributed Load Testing Using Kubernetes Reviews

Atul K. · Reviewed almost 2 years ago

Shivani F. · Reviewed almost 2 years ago

Mahmoud M. · Reviewed almost 2 years ago

Lab is broken (Please use the "gke-gcloud-auth-plugin" kubectl/client-go credential plugin instead.)

LTI S. · Reviewed almost 2 years ago

Rachid O. · Reviewed almost 2 years ago

Vimal Kumar V. · Reviewed almost 2 years ago

Amr E. · Reviewed almost 2 years ago

Sajjad E. · Reviewed almost 2 years ago

Humera N. · Reviewed almost 2 years ago

Sandy M. · Reviewed almost 2 years ago

Rajamohan N. · Reviewed almost 2 years ago

Malkapurapu S. · Reviewed almost 2 years ago

Nicolas T. · Reviewed almost 2 years ago

Abdul Rahman M. · Reviewed almost 2 years ago

Hissa A. · Reviewed almost 2 years ago

Winy A. · Reviewed almost 2 years ago

TC L. · Reviewed almost 2 years ago

Winetou R. · Reviewed almost 2 years ago

Ricardo L. · Reviewed almost 2 years ago

Hiteshkumar P. · Reviewed almost 2 years ago

CHIHABEDDINE F. · Reviewed almost 2 years ago

Task 6: Step 1 (example): sed -i -e "s/34.72.167.73/$TARGET/g" kubernetes-config/locust-master-controller.yaml sed -i -e "s/34.72.167.73/$TARGET/g" kubernetes-config/locust-worker-controller.yaml sed -i -e "s/qwiklabs-gcp-04-aee74564c756/$PROJECT/g" kubernetes-config/locust-master-controller.yaml sed -i -e "s/qwiklabs-gcp-04-aee74564c756/$PROJECT/g" kubernetes-config/locust-worker-controller.yaml Step 4 (command not boxed for whatever dumb reason and is between ... instead): kubectl apply -f kubernetes-config/locust-master-service.yaml

Brenden A. · Reviewed almost 2 years ago

Task 6 is a complete disaster and not explained well at all

Brenden A. · Reviewed almost 2 years ago

Ghada a. · Reviewed almost 2 years ago

Ghada a. · Reviewed almost 2 years ago