Setup Overview

CloudOps for Kubernetes is used to deploy and manage Elastic Path Commerce and Account Management on Amazon Web Service (AWS). For more information about planning your CloudOps for Kubernetes environments, go to the Project Workflow section. You can also review the Sample Configuration documentation.

The following workflow illustrates the process to setup CloudOps for Kubernetes:

Procedure

1. Review and verify the installation requirements are complete.

2. Prepare your AWS account for CloudOps deployment. For more information, see the Preparations Guide section.

3. Create a new Kubernetes cluster by bootstrapping CloudOps for Kubernetes using setup mode.

   note

   Ensure that Jenkins and Nexus pods are deployed to it. For more information about this process, see the Bootstrap documentation.

4. Complete the Post Bootstrap tasks.

Elastic Path Commerce

1. Build the Elastic Path Commerce artifacts. For more information, see the Build Deployment Packages and Build Commerce Docker Images sections.

2. Create a MySQL database by following the steps in one of the following links:

   • MySQL container - this database server type should only be used for development and transient environments.

   • MySQL Cloud Database Server - this database server type is suitable for production and production-like environemnts.

When implementing Staging and Production environment tiers, run this job twice to create an author and live database

1. Create an ActiveMQ service. For more information, see the Creating an Apache ActiveMQ Service section.

   For Staging and Production environment tiers, run this job twice to create author and live ActiveMQ instances.

2. Populate the database using the Data Population Tool. For more information, see the Populating an Elastic Path Commerce Database section.

   For Staging and Production environment tiers, run this job twice to populate the author and live database instances.

3. Deploy Elastic Path Commerce. For more information, see Deploying Elastic Path Commerce.

   For Staging and Production environment tiers, run this job twice to create an author and live stack.

   note

   Set the Jenkins parameter epChangesetsEnabled to true for the author environments in Staging and Production environment tiers.

4. (Optional) Repeat steps 7-10 for each environment tier in your planned architecture.

Elastic Path Account Management

1. Build Account Management Docker images

2. Provision an Account Management database

3. Deploy Account Management