http-consumer, geyser-consumer and graphql server have been moved to Kubernetes/AWS.
Sustaining infra is already in place and migration can be executed anytime.
Github actions pipeline is now connected to ArgoCD and deploying on Kubernetes on merge in dev and master branches.
Development workflow won't get impacted by this migration.
The only deployment that will be kept in heroku is metaplex-indexer, everything else will be migrated.
AMQP instances will remain hosted in Heroku for the time being.
Migration steps (DEV)
[x] Stand up sustaining infra in AWS (Writer DB + Follower DB)
[x] Spin up consumers and graphql server deployments in Kubernetes
[x] Wait for a full validator restart to allow the indexer to bring the DB up to date
[x] Connect ArgoCD to Github actions for CI/CD (Same as we have in heroku)
[x] Cert creation for graphql endpoint
[x] DNS Migration of graph-test.holaplex.com - point to Graphql in Kubernetes
http-consumer, geyser-consumer and graphql server have been moved to Kubernetes/AWS. Sustaining infra is already in place and migration can be executed anytime.
Github actions pipeline is now connected to ArgoCD and deploying on Kubernetes on merge in
devandmasterbranches.Development workflow won't get impacted by this migration.
The only deployment that will be kept in heroku is
metaplex-indexer, everything else will be migrated. AMQP instances will remain hosted in Heroku for the time being.Migration steps (DEV)
graph-test.holaplex.com- point to Graphql in Kubernetes