Setting up Infrastructure with CloudOps

Overview

This topic describes how to set up your team infrastructure with CloudOps for Kubernetes. We recommend you to understand and evaluate the advantages and disadvantages of CloudOps for Kubernetes before using it. For more information about deployment options, see Elastic Path Commerce Deployment Solutions.

CloudOps for Kubernetes

CloudOps for Kubernetes is a set of tools to provision and configure Kubernetes clusters using Amazon Elastic Kubernetes Service (EKS). The resulting Kubernetes cluster contains tools to build and test Elastic Path Commerce code, and to deploy Elastic Path Commerce applications in a very scalable and resilient manner. CloudOps for Kubernetes supports and requires Amazon Web Services (AWS) and uses a very specific architecture with a prescribed set of technologies.

tip

Elastic Path Commerce container images built using CloudOps for Kubernetes can also be run on any infrastructure that supports Docker-style containers. If you determine that CloudOps for Kubernetes is not suitable for your long term needs, there might be some advantage of using CloudOps for Kubernetes initially to quickly enable building and testing Elastic Path Commerce code.

For more information about CloudOps for Kubernetes, see CloudOps for Kubernetes documentation.

Prepare Elastic Path Commerce Source Code

Prerequisities

Ensure that you have the following:

Access to Elastic Path Commerce Source and Maven Repository
A development branch created in your Git Repository

For more details, see the Getting Access to Elastic Path Commerce Source Code section.

Setup Your Team Infrastructure

For more information about CloudOps for Kubernetes, see CloudOps for Kubernetes documentation.

Complete Elastic Path Commerce setup

This section provides instructions to complete setting up Elastic Path Commerce after setting up CloudOps for Kubernetes.

To complete the setup, configure the extensions/maven/settings.xml file to connect to the Nexus 2 artifact repository that is set up by CloudOps.

Checkout the development branch that you had created for your team/organization.

For more details, see the Getting Access to Elastic Path Commerce Source Code section.

Replace the PROJECT_REPOSITORY_GROUP_URL placeholder with the CloudOps DNS name of the project’s Nexus server. To construct the value, prepend nexus.ep-build in front of your project’s DNS name. For example, if DNS of the project is example.com, the CloudOps DNS name of the project’s Nexus server is nexus.ep-build.example.com. For more information, see DNS Configuration (Amazon Route53).
In the settings.xml file, make any other changes that are required by your project.
Commit and push the changes.

Setup Local Developer Environment

Follow the instructions at Setting up your Developer Environment to configure, build, and run Elastic Path Commerce in a command line environment.