fix: add kubectl wait before exec, increase pod crash and KEDA scaleout timeouts

Author: svennam92

website/docs/fastpaths/developer/amazon-eks-pod-identity/introduction.md

@@ -17,6 +17,7 @@ carts-dynamodb-698674dcc6-hw2bg   1/1     Running   0               14m
 In the output above, the Pod `carts-dynamodb-698674dcc6-hw2bg` is our lightweight DynamoDB service. We can verify our `carts` application is using this by inspecting its environment:
 
 ```bash timeout=180
+$ kubectl wait --for=condition=Ready pods -l app.kubernetes.io/component=service -n carts --timeout=120s
 $ kubectl -n carts exec deployment/carts -- env | grep RETAIL_CART_PERSISTENCE_DYNAMODB_ENDPOINT
 RETAIL_CART_PERSISTENCE_DYNAMODB_ENDPOINT=http://carts-dynamodb:8000
 ```

website/docs/fastpaths/developer/amazon-eks-pod-identity/tests/hook-pod-logs.sh

@@ -6,10 +6,10 @@ before() {
 
 after() {
   # The pod may need extra time to crash and have previous logs available
-  # Retry up to 180s re-fetching logs until we find the expected error
+  # Retry up to 240s re-fetching logs until we find the expected error
   LATEST_POD=$(kubectl get pods -n carts -l app.kubernetes.io/component=service --sort-by=.metadata.creationTimestamp -o jsonpath='{.items[-1:].metadata.name}')
 
-  for i in $(seq 1 18); do
+  for i in $(seq 1 24); do
     LOG_OUTPUT=$(kubectl logs -n carts -p "$LATEST_POD" 2>/dev/null || true)
     if [[ "$LOG_OUTPUT" == *"Unable to load credentials"* ]]; then
       echo "Found expected credential error in logs"

website/docs/fastpaths/developer/amazon-eks-pod-identity/understanding.md

@@ -5,9 +5,9 @@ sidebar_position: 33
 
 The first place to look for the issue is the logs of the `carts` service:
 
-```bash hook=pod-logs timeout=360
+```bash hook=pod-logs timeout=480
 $ LATEST_POD=$(kubectl get pods -n carts -l app.kubernetes.io/component=service --sort-by=.metadata.creationTimestamp -o jsonpath='{.items[-1:].metadata.name}')
-sleep 120
+sleep 180
 kubectl logs -n carts -p $LATEST_POD
 [...]
 software.amazon.awssdk.core.exception.SdkClientException: Unable to load credentials from any of the providers in the chain AwsCredentialsProviderChain(credentialsProviders=[SystemPropertyCredentialsProvider(), EnvironmentVariableCredentialsProvider(), WebIdentityTokenCredentialsProvider(), ProfileCredentialsProvider(profileName=default, profileFile=ProfileFile(sections=[])), ContainerCredentialsProvider(), InstanceProfileCredentialsProvider()]) : [SystemPropertyCredentialsProvider(): Unable to load credentials from system settings. Access key must be specified either via environment variable (AWS_ACCESS_KEY_ID) or system property (aws.accessKeyId)., EnvironmentVariableCredentialsProvider(): Unable to load credentials from system settings. Access key must be specified either via environment variable (AWS_ACCESS_KEY_ID) or system property (aws.accessKeyId)., WebIdentityTokenCredentialsProvider(): Either the environment variable AWS_WEB_IDENTITY_TOKEN_FILE or the javaproperty aws.webIdentityTokenFile must be set., ProfileCredentialsProvider(profileName=default, profileFile=ProfileFile(sections=[])): Profile file contained no credentials for profile 'default': ProfileFile(sections=[]), ContainerCredentialsProvider(): Cannot fetch credentials from container - neither AWS_CONTAINER_CREDENTIALS_FULL_URI or AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variables are set., InstanceProfileCredentialsProvider(): Failed to load credentials from IMDS.]

website/docs/fastpaths/developer/keda/install-keda.md

@@ -38,6 +38,8 @@ NOTES:
 After the Helm install, KEDA will be running as several deployments in the keda namespace:
 
 ```bash
+$ kubectl rollout restart deployment/keda-operator -n keda
+$ kubectl rollout status deployment/keda-operator -n keda --timeout=120s
 $ kubectl get deployment -n keda
 NAME                              READY   UP-TO-DATE   AVAILABLE   AGE
 keda-admission-webhooks           1/1     1            1           105s

website/docs/fastpaths/developer/keda/tests/hook-keda-pod-scaleout.sh

@@ -7,13 +7,13 @@ before() {
 after() {
   EXIT_CODE=0
 
-  timeout -s TERM 300 bash -c \
+  timeout -s TERM 600 bash -c \
     'while [[ $(kubectl get pod -l app.kubernetes.io/instance=ui -n ui -o json | jq -r ".items | length") -lt 2 ]];\
     do sleep 30;\
     done' || EXIT_CODE=$?
 
   if [ $EXIT_CODE -ne 0 ]; then
-    >&2 echo "Pods did not scale within 300 seconds"
+    >&2 echo "Pods did not scale within 600 seconds"
     exit 1
   fi
 }

website/docs/fastpaths/operator/amazon-eks-pod-identity/introduction.md

@@ -17,6 +17,7 @@ carts-dynamodb-698674dcc6-hw2bg   1/1     Running   0               14m
 In the output above, the Pod `carts-dynamodb-698674dcc6-hw2bg` is our lightweight DynamoDB service. We can verify our `carts` application is using this by inspecting its environment:
 
 ```bash timeout=180
+$ kubectl wait --for=condition=Ready pods -l app.kubernetes.io/component=service -n carts --timeout=120s
 $ kubectl -n carts exec deployment/carts -- env | grep RETAIL_CART_PERSISTENCE_DYNAMODB_ENDPOINT
 RETAIL_CART_PERSISTENCE_DYNAMODB_ENDPOINT=http://carts-dynamodb:8000
 ```

website/docs/fastpaths/operator/amazon-eks-pod-identity/tests/hook-pod-logs.sh

@@ -6,10 +6,10 @@ before() {
 
 after() {
   # The pod may need extra time to crash and have previous logs available
-  # Retry up to 180s re-fetching logs until we find the expected error
+  # Retry up to 240s re-fetching logs until we find the expected error
   LATEST_POD=$(kubectl get pods -n carts -l app.kubernetes.io/component=service --sort-by=.metadata.creationTimestamp -o jsonpath='{.items[-1:].metadata.name}')
 
-  for i in $(seq 1 18); do
+  for i in $(seq 1 24); do
     LOG_OUTPUT=$(kubectl logs -n carts -p "$LATEST_POD" 2>/dev/null || true)
     if [[ "$LOG_OUTPUT" == *"Unable to load credentials"* ]]; then
       echo "Found expected credential error in logs"

website/docs/fastpaths/operator/amazon-eks-pod-identity/understanding.md

@@ -5,9 +5,9 @@ sidebar_position: 33
 
 The first place to look for the issue is the logs of the `carts` service:
 
-```bash hook=pod-logs timeout=360
+```bash hook=pod-logs timeout=480
 $ LATEST_POD=$(kubectl get pods -n carts -l app.kubernetes.io/component=service --sort-by=.metadata.creationTimestamp -o jsonpath='{.items[-1:].metadata.name}')
-sleep 120
+sleep 180
 kubectl logs -n carts -p $LATEST_POD
 [...]
 software.amazon.awssdk.core.exception.SdkClientException: Unable to load credentials from any of the providers in the chain AwsCredentialsProviderChain(credentialsProviders=[SystemPropertyCredentialsProvider(), EnvironmentVariableCredentialsProvider(), WebIdentityTokenCredentialsProvider(), ProfileCredentialsProvider(profileName=default, profileFile=ProfileFile(sections=[])), ContainerCredentialsProvider(), InstanceProfileCredentialsProvider()]) : [SystemPropertyCredentialsProvider(): Unable to load credentials from system settings. Access key must be specified either via environment variable (AWS_ACCESS_KEY_ID) or system property (aws.accessKeyId)., EnvironmentVariableCredentialsProvider(): Unable to load credentials from system settings. Access key must be specified either via environment variable (AWS_ACCESS_KEY_ID) or system property (aws.accessKeyId)., WebIdentityTokenCredentialsProvider(): Either the environment variable AWS_WEB_IDENTITY_TOKEN_FILE or the javaproperty aws.webIdentityTokenFile must be set., ProfileCredentialsProvider(profileName=default, profileFile=ProfileFile(sections=[])): Profile file contained no credentials for profile 'default': ProfileFile(sections=[]), ContainerCredentialsProvider(): Cannot fetch credentials from container - neither AWS_CONTAINER_CREDENTIALS_FULL_URI or AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variables are set., InstanceProfileCredentialsProvider(): Failed to load credentials from IMDS.]