Opinie (Distributed Load Testing Using Kubernetes)

could not view replication controller using gcloud get rc, could not view locust page with external ip

Xin Ying L. · Sprawdzono ponad 7 lat temu

Alexander Z. · Sprawdzono ponad 7 lat temu

Instructions are outdated. 1. The YAML files need to be edited to populate the PROJECT_ID and the TARGET_HOST. This is not covered in the instructions. 2. Replication controllers are not used anymore as YAMLs switched to Deployment objects. As a result, some commands mentioned do not work. 3. Instructions on how to build an image of locust-tasks and push it to GCR are missing.

Alexander F. · Sprawdzono ponad 7 lat temu

sunil s. · Sprawdzono ponad 7 lat temu

Yujin B. · Sprawdzono ponad 7 lat temu

Michal F. · Sprawdzono ponad 7 lat temu

Instruction does not mention to set variables TARGET_HOST, PROJECT_ID before running kubernetes config yaml files. That results in lack of service running: google2897424_student@cloudshell:~/distributed-load-testing-using-kubernetes/kubernetes-config (qwiklabs-gcp-051a940289fdc188)$ kubectl get rc No resources found. google2897424_student@cloudshell:~/distributed-load-testing-using-kubernetes/kubernetes-config (qwiklabs-gcp-051a940289fdc188)$ kubectl get pods -l name=locust,role=master No resources found. --- google2897424_student@cloudshell:~/distributed-load-testing-using-kubernetes/kubernetes-config (qwiklabs-gcp-051a940289fdc188)$ kubectl get pods -l name=locust,role=worker No resources found. --- google2897424_student@cloudshell:~/distributed-load-testing-using-kubernetes/kubernetes-config (qwiklabs-gcp-051a940289fdc188)$ kubectl scale --replicas=20 replicationcontrollers locust-worker Error from server (NotFound): replicationcontrollers "locust-worker" not found --- $ kubectl get pods NAME READY STATUS RESTARTS AGE locust-master-9b48f5f57-cvbxm 0/1 InvalidImageName 0 18m locust-worker-79cfc76696-6t9s5 0/1 InvalidImageName 0 2m locust-worker-79cfc76696-7tb2b 0/1 InvalidImageName 0 2m locust-worker-79cfc76696-gwn4s 0/1 InvalidImageName 0 2m locust-worker-79cfc76696-ssxbn 0/1 InvalidImageName 0 2m locust-worker-79cfc76696-w6qnb 0/1 InvalidImageName 0 2m

Marcin S. · Sprawdzono ponad 7 lat temu

George D. · Sprawdzono ponad 7 lat temu

George D. · Sprawdzono ponad 7 lat temu

unable to deploy locust-master-controller

Mark C. · Sprawdzono ponad 7 lat temu

Miyashita T. · Sprawdzono ponad 7 lat temu

instruction wasn't clear that yaml file had to be edited, and was unable to recover from failed deployment.

Mark C. · Sprawdzono ponad 7 lat temu

Darien M. · Sprawdzono ponad 7 lat temu

incomplete tutorial

Aryo P. · Sprawdzono ponad 7 lat temu

19/03/19 - Lab 1

Diego Alejandro A. · Sprawdzono ponad 7 lat temu

5

Marek C. · Sprawdzono ponad 7 lat temu

Great

Diego Renato M. · Sprawdzono ponad 7 lat temu

Pandi H. · Sprawdzono ponad 7 lat temu

Very satisfied

Giovan I. · Sprawdzono ponad 7 lat temu

jiya m. · Sprawdzono ponad 7 lat temu

Lab is broken because of templated PROJECT_ID and TARGET_HOST. Please update the deployments and services to static images or add instructions for configuring our own GCR repositories

Jeff M. · Sprawdzono ponad 7 lat temu

Mada mada

Giovan I. · Sprawdzono ponad 7 lat temu

Moehammad Rady M. · Sprawdzono ponad 7 lat temu

Bayu A. · Sprawdzono ponad 7 lat temu