Unable to provision Postgress using Crossplane

Summary

I am trying out the feature added in Gitlab 12.5. I created a project, attached GKE Cluster to it. I also installed crossplane on to the cluster. Post installation of Crossplane, I have executed manual steps given on link. To provision PostgreSql, I tried ENV variables approach given on link but it didnt work. I also tried values.yaml approach with required changes in repository. But still the command kubectl get postgresqlinstance returns no resources found (Summarize the bug encountered concisely)

Steps to reproduce

(How one can reproduce the issue - this is very important)

• Create a Ruby/Spring project from template.
• Attach GKE cluster
• Install Crossplane
• Run manual steps needed to provision Postgres https://docs.gitlab.com/ee/user/clusters/crossplane.html
• Add values.yaml or env variables as per the instructions on https://docs.gitlab.com/ee/user/clusters/crossplane.html#auto-devops-configuration-options

Example Project

(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)

(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)

https://gitlab.com/mahendrabagul/my-ruby-project

What is the current bug behavior?

Postgres is not provisioned after following required steps

(What actually happens)

kubectl get postgresqlinstance returns no resources found

What is the expected correct behavior?

postgres should be provisioned.

(What you should see instead)

kubectl get postgresqlinstance should not return no resources found but instead it should return the postgres provisioned.

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)