-
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
task/WG-121: migrate to database VM #132
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally - pinged db within container. LGTM!
- name: DB_PASSWD | ||
valueFrom: | ||
secretKeyRef: | ||
name: postgres | ||
name: postgres-vm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@taoteg. fyi. in the services in kube that access the database, we have secrets/env-variables for database access. the previous secrets were stored under the name postgres
in kube but @sophia-massie and I save the new ones under postgres-vm
to not override the old ones. so we keep temporarily the old ones that work for the kube db and then also have the new ones that work for the new db vm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Overview:
This PR migrates to database VM:
kube/
)geoapi-database
(i.e. docker compose yml, postgress settings, readme, makefile which are all indevops/databae
)PR Status:
Related Jira tickets:
Notes:
I also put a top-level README in ~portal/ on geoapi-database VM: