Deploy a workload to run an application in one or more containers.
From the Global view, open the project that you want to deploy a workload to.
- Click Resources > Workloads. From the Workloads view, click Deploy.
Enter a Name for the workload.
Select a workload type. The workload defaults to a scalable deployment, by can change the workload type by clicking More options.
From the Docker Image field, enter the name of the Docker image that you want to deploy to the project, optionally prefacing it with the registry host (e.g.
registry.gitlab.com, etc.). During deployment, Rancher pulls this image from the specified public or private registry. If no registry host is provided, Rancher will pull the image from Docker Hub. Enter the name exactly as it appears in the registry server, including any required path, and optionally including the desired tag (e.g.
registry.gitlab.com/user/path/image:tag). If no tag is provided, the
latesttag will be automatically used.
Either select an existing namespace, or click Add to a new namespace and enter a new namespace.
Click Add Port to enter a port mapping, which enables access to the application inside and outside of the cluster . For more information, see Services.
Configure the remaining options:
Use this section to either specify environment variables for your workload to consume on the fly, or to pull them from another source, such as a secret or ConfigMap.
Use this section to add storage for your workload. You can manually specify the volume that you want to add, use a persistent volume claim to dynamically create a volume for the workload, or read data for a volume to use from a file such as a ConfigMap.
When you are deploying a Stateful Set, you should use a Volume Claim Template when using Persistent Volumes. This will ensure that Persistent Volumes are created dynamically when you scale your Stateful Set.
Amazon Note for Volumes:
To mount an Amazon EBS volume:
Click Show Advanced Options and configure:
- Labels & Annotations
- Security and Host Config
Result: The workload is deployed to the chosen namespace. You can view the workload’s status from the project’s Workloads view.