---
# System prepended metadata

title: GLXY infrastructure reorganisation
tags: [k8s, AWS, Kluwer]

---

###### tags: `Kluwer` `k8s` `AWS` 

# GLXY infrastructure reorganisation  

## Downsizing

### 1. RabbitMQ migration

- setup vhosts in rabbitmq (VM version)
- update configuration for the services to use the new rabbitmq environment
- rabbitmq k8s (helm chart)
- TODO : move to GBS managed environment

### 2. MarkLogic

- setup VM's for the different ML env (minimum for the non-prod and staging) with latest ML versions
- setup security groups
- install security agents
- backup restore data to new marklogic servers
- update dns to point to the new marklogic servers
- Remove ML clusters (non-prod/prod) in Rancher
- Delete VM's in AWS
- update targetgroups/NLB's

### 3. Downsizing k8s

- Reduce servers in non-prod AWS cluster to 1 (augment capacity of the remaining server if required)
- Reduce server in prod AWS cluster to 1 (augment capacity of the remaining server if required)


## Rancher migration to latest version

- Setup new rancher server with latest version
- install security agents
- Add new prod / non-prod AWS environment 
- install security agents
- Add new prod / non-prod onPremise environment
- Update deployment script for k8s for a new development environment
- Test deployment of AWS/onPremise stack to the new dev k8s environment
- Migrate tst,at, uat, stg, prod in this order (deploy + dns update)
- Decommission the old k8s env
