Deployment Architecture Upgrade
Last updated
Was this helpful?
Last updated
Was this helpful?
This document outlines the steps required for migrating the deployment architecture from V2 to V3.
This is required for migration from V2 to V3 architecture
Make sure to have all the pre-requisites ready as per the details present in the section
Setup Wireguard
Setup wireguard client in your local and complete the
Setup
Configure
Observation cluster’s
Observation cluster
Observation cluster
Setup new
MOSIP k8 cluster
MOSIP cluster
Setting up for MOSIP cluster
Setting up for MOSIP cluster
Setting up for MOSIP cluster
(Required for V2 to V3 architecture migration)
Note:
i. Deploy postgres server in a seperate node.
ii. Make sure postgres initialisation is not done (only install postgres).
Note: Make sure keycloak initialisation is not done (only install keycloak).
Note: These instructions are only applicable if you need to access Private Docker Registries. You may disregard them if all of your Docker containers are downloaded from the public Docker Hub.
This step is required for V2 to V3 architecture migration.
Softhsm (only required if softhsm is used instead of real HSM)
iii. Update softhsm ida and softhsm kernel security pin
Postgres
iii. secret creation
iv. Increase postgres max_connections
to 1000
Keycloak
Minio
i. Export the existing Minio as directory
Kafka
i. setup external minio for backup.
ii. backup kafka
iii. restore kafka
Conf-secrets
dmz-sc.yaml
dmz-pkt-pv.yaml
dmz-pkt-pvc.yaml
dmz-landing-pv.yaml
dmz-landing-pvc.yaml
Setup
Setup
Setup
Setup
Setup
Setup
Setup
Setup docker if you are using private dockers.
Setup for the required domains.
Setup for new MOSIP cluster.
i.
ii.
i.
ii.
i.
ii.
ii.
Update the secrets in existing secrets in .
Packets in landing to be copied from old environment to the upgraded environment or same NFS folder can be mounted to regproc packet server and group 1 stage groups. Refer for more details.