-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minimal first version #2
base: main
Are you sure you want to change the base?
Conversation
I managed to start a deployment with one container, and I could see from the logs that this is up and running. The problem I am currently facing and I am a bit stuck is about sending a request to the container, I am not sure the configuration I developed is correct:
I am clearly missing a part of the configuration: do I have to create a dedicated service in charge of routing the requests to the appropriate container? |
To test locally, it is easier to use 'kubectl port-forward'. Inside the cluster, dispatcher can access your new pod through a service you need to create. |
Thanks, this worked for me and I could finally test it locally
Ok, I will define also a specific service |
With the last development:
|
I am missing the following part: Within the |
Inspired by create-secret , I figured it out. The dispatcher config (for the dispatcher container), as well as the postgres password, are included in a secret |
Following the doc in https://hub.docker.com/_/postgres/ , I developed an entrypoint script that creates the DB, schema and installs the extension |
No description provided.