Skip to content
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

Configure k8s services for rolling updates #170

Open
gothub opened this issue Nov 15, 2018 · 1 comment
Open

Configure k8s services for rolling updates #170

gothub opened this issue Nov 15, 2018 · 1 comment
Assignees
Labels
metadig All issues related to metadig metadig-k8s Metadig kubernetes configuration
Milestone

Comments

@gothub
Copy link
Contributor

gothub commented Nov 15, 2018

Rolling updates are support by k8s, as described here. With this capability, new versions of MetaDIG services could be installed without downtime.

@gothub gothub added metadig All issues related to metadig metadig-k8s Metadig kubernetes configuration labels Nov 15, 2018
@gothub gothub added this to the 2.0.1 milestone Nov 15, 2018
@gothub gothub self-assigned this Nov 15, 2018
@gothub gothub modified the milestones: 2.0.1, 2.1.0 Jan 30, 2019
@gothub gothub modified the milestones: 2.1.0, 3.0 Apr 2, 2020
@jeanetteclark
Copy link
Collaborator

This is mostly implemented, however I did run into an issue with updating the postgres schema yesterday.

@mbjones suggested we have all of the other containers (worker, controller, scorer, scheduler) start with an initContainer that makes sure pg is operational before they start. Here is an example: https://github.com/DataONEorg/dataone-indexer/blob/develop/helm/templates/deployment.yaml#L69

This is likely tied to #354

@jeanetteclark jeanetteclark modified the milestone: 3.0 Jul 7, 2023
@jeanetteclark jeanetteclark modified the milestones: 3.0, 3.1 Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
metadig All issues related to metadig metadig-k8s Metadig kubernetes configuration
Projects
Status: Backlog
Development

No branches or pull requests

2 participants