AutoDevops deployment fails - Postgres helm deployment times out

Context: Simple rails API - app deployment using AWS integration and gitlab autodevops

Issue: First time deployment fails at postgresql deployment with timeout

Describe your question in as much detail as possible:
The Application is a simple rails API app with a postgres DB. I have an Amazon EKS cluster (on fargate) which was successfully linked with gitlab.
The Deployment stage however fails because of a timeout during helm chart deployment of postgresql.
Am unable to go past this stage.

  • What are you seeing, and how does that differ from what you expect to see?
    Relevant error logs from the pipeline at deployment stage:
$ auto-deploy deploy
Error: release: "staging" not found
Release "staging-postgresql" does not exist. Installing it now.
Error: release staging-postgresql failed: timed out waiting for the condition
Successfully purged a chart!
Error: release staging-postgresql failed: timed out waiting for the condition
  • Consider including screenshots, error messages, and/or other helpful visuals

  • What version are you on? Are you using self-managed or

  • Add the CI configuration from .gitlab-ci.yml and other configuration if relevant (e.g. docker-compose.yml)
    No Docker file or gitlab ci file was present. however I did create an auto-deploy-values.yaml to overwrite default helm chart values for service port

  internalPort: 3000
  externalPort: 3000
  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
  1. This troubleshooting section seems to point to a similar problem, but it only seems to be an issue for service ports, and not DB ports.
  2. I even tried to skip that stage by adding the following as my file:
  - template: Auto-DevOps.gitlab-ci.yml


However $ auto-deploy deploy still attempts to install the staging-postgresql release, and fails:

I just want autodevops to successfully deploy my app onto the cluster, with or without postgres deployment being managed by gitlab…

How do I work around this?