OCP4 Migration Coordination - Githubissues

bcgov / von-bc-registries-agent-configurations

Build and Deployment Configurations for the Indy-Catalyst version of the BC Registries Agent

Apache License 2.0

0 stars 7 forks source link

OCP4 Migration Coordination #47

Closed esune closed 3 years ago

esune commented 3 years ago

Deadline: Everything must be migrated to OCP4 by April 30th, 2021.

Components:

agent, bcreg-controller and event-processor must use the same image currently running in production in OCP3
all remaining services can use the latest image from the repository
the build in the db component should be updated to the latest version before migrating - see #46
schema-spy will likely need to be updated following what was done in orgbook-configurations (low priority)

Secrets:

All secrets should be configured to use the same values as in OCP3

Related:

See this issue in orgbook-configurations for the related work on the OrgBook side.

esune commented 3 years ago

agent, bcreg-controller and event-processor have been build off the latest commit running in OCP# prod and tagged as ocp3-prod.

All deployments have been recreated using the same secret values as in OCP3 - with the exception of schema-spy that will need to be updated further to match what is in orgbook-configurations.

esune commented 3 years ago

Closing this as migration is now complete.