Polkadot Cloud-Native CICD Tool
A [Cloud Native Computing Foundation](cncf.io) compliant CICD tool - a DevOps culture solution
Created on 30th May 2021
•
Polkadot Cloud-Native CICD Tool
A [Cloud Native Computing Foundation](cncf.io) compliant CICD tool - a DevOps culture solution
The problem Polkadot Cloud-Native CICD Tool solves
Continuous Integration and Deployment of CN-compliant containers to a Highly-Available, Self-Healing Kubernetes Platform. Integration in itself is hard to do, and re-invention is rampant practice. What if a tool exists that can quickly ramp up development, testing and deployment, and cycle feedback for more advanced features, making deployments at improved speeds. What if a service exists that can quickly spawn or provision a custom-made blockchain platform and its applications? What if we can auto-provision and deploy features quickly. What if we can deploy parachains, validators, collators on-demand in a consistent automated manner?
Challenges we ran into
Docker builds in local requiring larger memory than the 2 Gig Docker default was a painful and expensive realization. Builds in our servers were dragging and Github builds takes over an hour. Increasing memory for Docker in our local. Same for VMs. We think that in order to solve the Github build, we will need to terraform an AWS spot instance that is large enough (such 32 - 64Gb with 10 or more cores) to improve the parallel builds. Why do we have to custom-build containers, especially Docker? Well, for the security contexts, we think the user 1000 is reserved for the first user in Linux OS. So using 1001 is more precise for Polkadot as an app. Ports 9615 for Prometheus needs to be exposed so that we could access its metrics end-points in an openshift prometheus and grafana pods.
Technologies used