docker login repository.broadleafcommerce.com:5001
- v1.0.0-latest-prod
Now that you have your own container images built and deployed to your own registry, you can now utilize our example Helm charts as a starter to deploy your various Broadleaf Flex Package compositions to an existing Kubernetes cluster (which can be created with the reference Terraform scripts mentioned above). See the Deployment Flexibility article for more details if you’re not familiar with Broadleaf’s Flex Package technology.
|
Note
|
Please see the README on the "Helm Charts Starter" project that is included with the Microservice Project Starters. This project provides a base starting point that you can use as a reference for your specific deployment as well as provides a sample install.sh script to deploy all the resources requirerd in a full Broadleaf installation containing all the demo starter images
|
|
Important
|
All references to a "Starter Project" or "Demo Images" assumes you have obtained credentials outlined in the guide: Getting Started Locally and you have the ability to authenticate with Broadleaf’s docker registry and maven nexus. e.g. |
The following tables describe the various demo images that are produced and used across the different Microservice Starter Projects. This serves as a general reference to their relative location within the starter Helm charts.
|
Note
|
typically the image tag versions defined in the starter project’s charts represent the latest stable releases of the current demo |
| Pod | Primary Container Image | Helm Chart |
|---|---|---|
Backoffice Admin Gateway |
|
|
Backoffice Admin |
|
|
Auth Service |
|
|
Customer Facing Storefront Gateway |
|
|
Customer Facing Storefront |
|
|
Kafka |
|
|
Open API UI |
|
|
Solr |
|
|
Zookeeper |
|
|
| Name | Typical Helm Installation | Notes |
|---|---|---|
Kube Prometheus Stack |
|
Typical Broadleaf overrides and settings can be found in: |
Elastic Stack |
|
Sample APM Server and Filebeat config are located in |
The following sections represent the different images used depending on which example flex package composition you choose to deploy for your core commerce backend services.
| Pod | Primary Container Image | Helm Chart |
|---|---|---|
|
|
|
|
|
|
| Pod | Primary Container Image | Helm Chart |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note
|
(*) The Processing Flex Package has some unique properties wherein some services are only included with input listeners for import and sandboxing transitions ONLY (and will be exempt from servicing typical request traffic). i.e. heavy back office functions can be scaled independently while not impacting customer facing browse flows or vice versa. |
The following represents all the services deployed individually.
| Image | Helm Chart |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|