ci(k8s-e2e): increase readiness timeout

Author: DavSanchez

test/k8s-e2e/apm/e2e-apm.yml

@@ -17,7 +17,7 @@ scenarios:
       - kubectl create -f ./rubyapp.yaml --dry-run=client -o yaml | sed s/placeholder/${SCENARIO_TAG}-ruby/ | kubectl create -f -
 
       # Generate some traffic
-      - kubectl wait --for=condition=Ready --all pods --timeout 5m
+      - kubectl wait --for=condition=Ready --all pods --timeout 10m
       - timeout 60s bash -c "until kubectl exec ${SCENARIO_TAG}-python -c ${SCENARIO_TAG}-python -- wget -qO /dev/null 127.0.0.1:8080; do echo 'Python not ready yet. Retrying...';sleep 5;done"
       - seq 100 | xargs -I{} kubectl exec ${SCENARIO_TAG}-python -c ${SCENARIO_TAG}-python -- wget -qO /dev/null 127.0.0.1:8080
       - timeout 60s bash -c "until kubectl exec ${SCENARIO_TAG}-node -c ${SCENARIO_TAG}-node -- wget -qO /dev/null 127.0.0.1:3000/rolldice; do echo 'Node not ready yet. Retrying...';sleep 5;done"