Deploying Local Edition Using Helm Charts

Local Edition is deployed on Kubernetes or OpenShift using Helm Charts.

Before deploying the application, verify that the required resources are available and are accessible. For more information, see Prerequisites and Preinstallation Checklist.

Local Edition is stateless and can spread across availability zones (AZ). Based on your organizational IT policies, configure the pods for:

• Define pod topology spread constraints.

• Define pod affinity rules and tolerances.

• Follow the Kubernetes best practices of spreading nodes across zones.

Pods and Images (introduced in v6.1.0)

important

This section was added in the Boomi Cloud API Management – Local Edition (LE) 6.1.0 release.

Image name	Podname/Container name	Notes
fluent/fluent-bit	All replica sets (trafficmanager, platformapi, ConfigUI, cache, loader)	This is optional. Users can choose not to include it by setting includeFluentBitContainer to false.
distroless		All other replica/deployment pod containers use this as a base image.
apim-jre-base		All Java container images use this as a base.
apim-le-trafficmanager	trafficmanager-deploy/trafficmanager
apim-le-platformapi	platformapi-deploy/platformapi
apim-le-loader	loader-deploy/loader
apim-le-cache	cache-deploy/cache
apim-le-configui	configui-deploy/configui
apim-le-loader-cron	loader-job-delta
	loader-job-full
	postInstallDataLoad-job
apim-le-toolkit	preInstallDataPrep-job
	postUpgradeDataLoad-job
	Ephemeral/Debug containers

Steps to deploy the application

warning

This guidance was introduced in Boomi Cloud API Management - Local Edition (LE) 6.1.0 release:

When deploying the application in OpenShift, create a new project and deploy the application in that project. Do not use the default project, as it has multiple restrictions on resource management. Refer to Openshift Deployment for more information.

1. Depending on which LE 6.x version you are using, provide values using the overrides file or by editing values.yaml. We recommend using the overrides file.

   Refer to the following values.yaml files in:

   • LE 6.2.0: 6.2.0 Values.yaml.

   • LE 6.1.0: 6.1.0 Values.yaml.

   Edit values.yaml and provide the configuration in:

   • LE 6.0.0: 6.0.0 Values.yaml.

2. Customize the Fluent Bit template as per your observability requirements.

3. Deploy the application using Helm.

4. Verify that the application is ready.