A Workload in Otomi is a self-service feature for creating Kubernetes resources using Helm charts from the Otomi Developer Catalog.
All Workloads of the team are listed here.
|The name of the workload
|Link to the Argo CD application in the Argo CD UI
|Image update strategy
|The configured update strategy for the workload
|The status of the workload. Click on the Argo CD application link to see more status details
Create a Workload
Before creating a workload from the developer catalog, we'll need the
tag of the image you would like to use.
Go to the list of Builds and add the
repositoryof the build to use to your clipboard. Remember the tag.
Workloadsin the left menu and click on
Select a template from the catalog to use
Namefor the workload
(Optional) Configure the
Auto image updater. Default is
The Auto Image Updater will (based on the update strategy) automatically update the container images of a workload.
Select the update strategy. Choose between:
- Digest: Inspects a single tag in the registry for changes, and updates the image on any change to the previous state. Requires to provide a
- Semver: Update based on semantic versions. Example:
v1.0would allow the image to be updated to any patch version within the 1.0 minor release.
There are 2 other properties available:
tagParameter. Change the parameters in case your Helm application contains more than one image in the manifests or uses another parameters to define which image to render in the manifests.
- In the workload
values, change the following parameters:
repository: <paste from clipboard>
Now click on
After a few minutes, Otomi will have created all the needed Argo CD resources to deploy your workload. In the workloads list, click on the
Application link of your workload to see the status of your workload.
The values of a workload can be changed at any time. Changes will automatically be deployed.