Hi Team.
My Environment:
Amazon EKS 1.19 w/Managed hosts
Amazon RDS Postgres 12.5R1
AWX Operator 0.8.0
AWX deployment yml file:
##File.yml##
(attachments)
awx-42821-1.log (1.46 MB)
Hi Team.
My Environment:
Amazon EKS 1.19 w/Managed hosts
Amazon RDS Postgres 12.5R1
AWX Operator 0.8.0
AWX deployment yml file:
##File.yml##
awx-42821-1.log (1.46 MB)
well… operator 0.9.0 made the trick, that version fixes connectivity to external (unmanaged) PostgreSQL databases.
I’m having similar issues, but have upgraded to 0.9.0 with no success:
Amazon RDS Postgres 12.5R1
minikube 1.12.1 (but will be running on rancher in production)
AWX Operator 0.9.0
After the awx deploy, I see the following in the logs:
django.db.utils.OperationalError: SSL error: certificate verify failed
FATAL: no pg_hba.conf entry for host “x.x.x.x”, user “user_i_created”, database “awx”, SSL off
where x.x.x.x is the IP of the host I am not and not the DB. I have used this RDS instance for my existing (16.0.0) implementation so the host/user/db/password are all correct.
Not sure where else I can look or what I can set to get this working
I didn’t have that particular issue, in my case it wouldn’t even try to connect to the database. For the new operator version to work I made some changes to my yaml file, in bold below. Did you try those? I also made sure that the security group in RDS accepts connections from the k8s cluster network.
Yes, I have been using those options in bold and they don’t help.
I can connect just fine via psql and awx-manage dbshell, that’s what is confusing me.
Did you create the database in RDS?
I had the same issue, then I found out the awx-* containers were trying to connect to a database that didn’t exist in the RDS host.
Hi folks,
I am trying to create AWX tower in EKS fargate and would like to use the external rds database connection.
And following the below GitHub documentation
https://github.com/ansible/awx-operator
As was able to successfully run the awx-operator control manager.
But when I tried to deploy the AWX yaml file it creates a awx-postgres pod which will be in pending state with pod doesn’t support fargate and when I deep dive into it it’s looking for persistantvolume and persistent volume claim.
Questions here:
When I am trying to say to use external db, why it’s again deploying db pod.
If it’s mandatory that even after mentioning to use external db, it needs the and db pod running.
Please help me out here i struggling to find the information