After the infrastructure in Azure is setup, you are ready to start deploying the Elastic Path stack.
Note: To deploy two Elastic Path stacks, such as an authoring and a live environment in the same AKS, Azure Kubernetes Services, cluster make sure to deploy each environment into its own Kubernetes namespace.
If both Elastic Path stack deployments need to use the Azure Database for MySQL Server, repeat the instructions in the Creating and Populating the Database section.
Deploying Elastic Path Commerce using Jenkins
Run the Jenkins job
deploy-or-delete-ep-stack with the following parameters:
Parameters for the
deploy-or-delete-ep-stack Jenkins Job
|When selected, this deletes the stack instead of creating it.|
|The Git repository URL of the cloudops-for-azure code.|
|The branch of cloudops-for-azure to use.|
|The type of environment and configuration of your ep-stack, such as, CI, production, or staging.|
|The tag of the ep-app Docker images to use.|
|The namespace in the Kubernetes cluster to deploy the Elastic Path stack into. This namespace must have a deployment of a data populated MySQL database.|
|Creates or deletes Ingresses to allow connections from the |
|The network CIDR the Ingresses allow to access the stack. Ignore this parameter if |
|Creates or deletes horizontal pod autoscalers. It automatically scales the number of pods in the deployment based on CPU usage. The default setting is false.|
|Creates or deletes a page displaying AKS cluster details, database details, and links to the deployed applications. The default setting is false.|
|If set to true, UI tests are enabled for the deployment. The default setting is false.|
|If it is set to |
|Deploys or deletes the Data Sync tool webapp. The Data Sync Tool (DST) can only be deployed if epChangesetsEnabled is |
|The Kubernetes namespace of the target database that the DST pushes changes to. Leave empty if |
|The name of the target server created by create-or-delete-activemq-container that the DST publishes syndication events to. Leave empty if |
|The name of the target database that the DST pushes changes to. Leave empty if |
|A subdomain to be prepended to the |
For example, if
|The name of the AKS cluster to deploy the ep-stack into. The |
|The address of the SMTP server. |
For example, if using SendGrid as an SMTP service provider, the value would be
|The port number of the SMTP server. Do not set this value to 25 as Azure blocks outgoing connections on port 25. |
For example, if you are using SendGrid as an SMTP service provider, you could enter a value of
|Use one of the following schemes when connecting to the SMTP server:|
|The username to use when connecting to an SMTP server.|
|The password to use when connecting to an SMTP server.|
|The name of the database created by either create-mysql-server or create-mysql-container.|
|The name of the server created by create-or-delete-activemq-container.|
|The image tag to use for the wait-for container.|
|This enables connecting to the app JMX ports. The default setting is false.|
|This enables connecting to the application Java Virtual Machine (JVM) debug ports with the remote debugger of your IDE. The default setting is false.|
This option deploys an Elastic Path stack with Ingresses that whitelist a CIDR in the parameter
allowedCIDR. The default value 127.0.0.1/32 in
allowedCIDR effectively does not allow any access. The Elastic Path stack won’t allow incoming connections and you cannot access your applications via the DNS endpoints unless Ingresses are created and your CIDR is in the job parameter
WARNING: Attempting to create Ingresses with no value in
allowedCIDRresults in a failed deployment. It is strongly suggested to test that the annotation is working correctly.
Creating Horizontal Pod Autoscalers
This option deploys an Elastic Path stack with Horizontal Pod Autoscalers. For more information, see Horizontal Pod Autoscalers
Creating Deployment Information Page
This option deploys an Elastic Path stack with a deployment information page. You can deploy the deployment information page alongside your applications to display AKS cluster details, database details, and links to the deployed applications. For more information, see the Example Information Page image.
WARNING: The deployment information page is not secured beyond IP whitelisting. It is intended for use with test environments. Do not deploy alongside production environments.
Choosing to create the Deployment Information Page exposes the ActiveMQ admin console to the public internet according to the whitelist-source-range set during configuration, with no additional security.
The paths to the info-page and ActiveMQ, from root DNS for your deployment are defined as
The paths to the info-page from root DNS for your deployment are defined as
The paths to ActiveMQ from root DNS for your deployment are defined as
Deploying with UI Tests Enabled
This option deploys an Elastic Path stack with UI Tests enabled.
Deploying with Changeset enabled
This option deploys an Elastic Path stack with changeset enabled.
Deploying with the Data Sync Tool Webapp enabled
This option deploys an Elastic Path stack with the Data Sync Tool (DST) as a command-line tool and as a Java application. The DST can only be deployed as a Java application on Elastic Path version 7.5 or later. Deploying the DST requires values for the
For more information about the Data Sync Tool, see Elastic Path Production Tools.
Deploying with JMX Enabled
This option allows connections to JMX for the Elastic Path stack with a java profiler. For more information, see the Connecting to the Applications JVM’s section.
Deploying with Debug Enabled
This option allows connections to the JVM in debug mode from your IDE. For more information, see the Connecting to the Applications JVM’s section.
deploy-or-delete-ep-stack job can take approximately 15-30 minutes to complete as it waits for the stack to become available.
Open the Kubernetes dashboard and select the namespace you used when you ran the
Validate that the following Deployments are present:
- Validate that the following Services are present:
Validate that a ConfigMap named
deployDstWebappis true, validate that a secret named
Ensure that you are able to see the ConfigMap
ep-configmap in the chosen namespace in the Kubernetes dashboard. The ConfigMap is a key/value store that can be used to set environment variables on each of the containers running in the Kubernetes Deployment.