In the case of a freshly created or a slower cluster, the RHDH deployment can take a longer time to start up (the `backstage-backend` pod). This happened specifically with a fresh GKE cluster and an ephemeral spot AKS cluster.

This can result in exceeding the time that is set in the `startupProbe` that then restarts the pod after the specified time. This can result in `CrashLoopBackOff` for `backstage-backend` pod. 

The probable solution is to set the probe `failureThreshold: 9` while keeping other values as is. The desired time to start-up can be adjusted with different variables.

We should increase this for both the Helm chart and the Operator.

After it is increased in the Helm chart and https://issues.redhat.com/browse/RHIDP-5770 is done, we can remove the probe overrides from:

• .ibm/pipelines/value_files/values_showcase.yaml
• .ibm/pipelines/value_files/values_showcase-rbac.yaml

Related conversation on Slack: https://redhat-internal.slack.com/archives/C06SGFD65NC/p1737451597499919