Elastic Path CloudOps for Kubernetes is Elastic Path’s automated approach to run Elastic Path Commerce inside of a Kubernetes cluster in a cloud-agnostic fashion. CloudOps for Kubernetes uses industry standard tooling, such as Terraform and Helm, to create highly scalable environments, built from Elastic Path Commerce code.
By utilizing CloudOps for Kubernetes, users are able to have the Elastic Path Commerce solution running in either AWS or Azure in a short period of time. With Kubernetes’ tooling, developers can quickly customize and deploy stacks. Given the broad adoption and standardization on Kubernetes, Ops teams have a solution to which they trust and that adapts to their needs.
Build and Deployment Features
CloudOps for Kubernetes provides a way to build and run a deployment of the Elastic Path Commerce stack. With CloudOps for Kubernetes, you can:
- Bootstrap an auto-scaling, load balancing Kubernetes cluster using either the Azure AKS service or the AWS EKS service with the Ambassador API Gateway providing traffic routing
- Use the included Jenkins server to build Docker images from Elastic Path Commerce source code and an Account Management release package. Push them into ACR (Azure Container Registry) or ECR (Elastic Container Registry).
- Create and populate a MySQL database with catalog content
- Deploy the Elastic Path stack using the built Docker images
Elastic Path CloudOps for Kubernetes does not test any of the artifacts, do production-grade monitoring, or logging infrastructure for the deployment.
For users evaluating CloudOps for Kubernetes, you must ensure that the scaling of nodes in a Kubernetes cluster provisioned and managed by the cloud provider is thoroughly tested. As a result, it is encouraged for anyone evaluating CloudsOps for Kubernetes to thoroughly test scaling of the pods and Kubernetes cluster nodes in different production-like scenarios.