but present in: "manifests/sock-shop-ns.yaml"

Not sure how complete-demo.yaml is actually generated

From the readme I understand that the dm-setup folder's code ensures Google Deployment Manager running in one project deploys GCP resources in another project.

Something that I could not catch hold of is

1. How do you set the target project details where the cluster would need to get deployed ?

Steps to install kubectx/kubens on Debian:
mkdir bin
export PATH=$PATH:~/bin/
sudo git clone https://github.com/ahmetb/kubectx ~/kubectx
sudo ln -s ~/kubectx/kubectx ~/bin/kubectx
sudo ln -s ~/kubectx/kubens ~/bin/kubens

Hi
I have tried to install clusters based in dm-setup. I am attaching the istio-system pods and output of statsd

pamir_erdem@advanced-kubernetes-215013:~ kubectl get pods -n istio-system
NAME READY STATUS RESTARTS AGE
istio-citadel-7bdc7775c7-zpv7n 1/1 Running 0 5h
istio-egressgateway-795fc9b47-g6jtj 1/1 Running 0 5h
istio-ingress-84659cf44c-mkpxl 1/1 Running 0 5h
istio-ingressgateway-7d89dbf85f-xxf7q 1/1 Running 0 5h
istio-pilot-66f4dd866c-fxnmh 2/2 Running 0 5h
istio-policy-76c8896799-j7mwn 2/2 Running 0 5h
istio-sidecar-injector-645c89bc64-mlczt 1/1 Running 0 5h
istio-statsd-prom-bridge-949999c4c-2kt2d 0/1 CrashLoopBackOff 66 5h
istio-telemetry-6554768879-qlbsn 2/2 Running 0 5h
prometheus-86cb6dd77c-vrtqs 1/1 Running 0 5h
pamir_erdem@advanced-kubernetes-215013:~$ kubectl logs -n istio-system istio-statsd-prom-bridge-949999c4c-2kt2d
statsd_exporter: error: unknown short flag '-s', try --help

steps to install helm on Debain:

curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > get_helm.sh
chmod 700 get_helm.sh
./get_helm.sh

The student VM does not have Docker installed, which is needed for module 2.

This is likely a bug in DM or the way we are setting up the IAM binding.

If you create the DM template and then delete it, the service account for the student VM is deleted but the role binding on the project still exists. When the deployment is created again the binding is not updated to point to the new SA (with the same name).

I received this error while going through the DM setup:

googlece5877_student@cloudshell:~/advanced-kubernetes-bootcamp/dm-setup (qwiklabs-gcp-f9008da2cc63b81c)$ gcloud deployment-manager deployments create --config workshop.yaml adv-bc-$(date +%s)
The fingerprint of the deployment is EWIlUgcwxyLmlSYvyuOy9A==
Waiting for create [operation-1530022889459-56f8c36d30d39-5af38a2c-952c9943]...failed.
ERROR: (gcloud.deployment-manager.deployments.create) Error in Operation [operation-1530022889459-56f8c36d30d39-5af38a2c-952c9943]: errors:

• code: RESOURCE_ERROR
  location: /deployments/adv-bc-1530022888/resources/student-vm-21561737771-waiter
  message: '{"ResourceType":"runtimeconfig.v1beta1.waiter","ResourceErrorCode":"504","ResourceErrorMessage":"Timeout
  expired."}'

Steps to install hey on Debian:
go get -u github.com/rakyll/hey

Hi,
The command below creates 3 kubernetes clusters and does not create necessary pods and deployments like istio prometheus spinnaker
gcloud deployment-manager deployments create --config workshop.yaml adv-bc-$(date +%s)

Also i deleted all service accounts associated with dm's deployment. Are there any additional tasks to do? When you delete service accounts only prometheus is deployed. Could you please assist me to re create the lab environment in the same project.

regards.

A premium (i.e. non-trial) Stackdriver account is needed for module 3 (at least) -- double-check and confirm that the Qwiklab environment provides this. Recording this here so it doesn't get lost.

From cloudshell it is trivial to run an ssh tunnel to the Spinnaker UI port, and connect directly via the browser -- from the Student VM this is not achievable in the same way because kubectl port-forward listens on local ports only so cannot be accessed remotely.

When using sock-shop app on frontend logs