Hi, So I followed the Pactflow doc for running my enterprise image on my local. (https://docs.pactflow.io/docs/on-premises/docker-compose-example/) I got a docker-compose script from the pact docs. On placing that docker-compose.yml file with my pactflow.lic file I was able to run the enterprise image on my local. NOW, I am trying to deploy it to Kubernetes via deployment scripts but I am facing the following issue. "The postgres container is up in my pod along with pactflow container, but the pactflow container is unable to talk to postgress" I am suspecting this has something to do with this docker-command (See screenshot below) How can I apply the same configuration in my Kubernetes deployment yaml script? (Attached the deployment script and logs given by my kubernetes team)

So that says “wait for the

postgres

container on port

5432

to be available”

Thanks for your response Matt. Was able to figure it out and finally was able to see the UI. However, the UI is not responding. There is a broken "Pactflow Demo Auth" button which is not responding on clicking. Can you please guide me on where I can find the root cause for this? Really greatful for your help so far!

It looks like the image is not loading properly. Are there any errors in the network console or PactFlow logs?

The page is not at all responding on the button click.

So those are CSP headers, and are critical to ensuring your app is safe from common web-based attacks

Thanks a lot @Matt (pactflow.io / pact-js / pact-go)! You were right all our configurations were pointing to localhost. Finally the image is deployed on our PKS and up and running! Finally! 🥳

Fantastic - well done! 👏