provision job is used to create ancillary objects like load balancers on Container Orchestration Platforms. Currently we support provisioning of load balancers on clusters hosted on:
- Google Container Engine (GKE)
- Azure Container Service (AKS)
Please note that when
provision jobs are deleted, the resulting objects are also deleted from the container service.
You can create a
provision job by adding it to
jobs: - name: <string> # required type: provision # required dependencyMode: <chrono/strict/immediate> # optional on_start: # optional - NOTIFY: <notification resource name> steps: - IN: <loadBalancer> # required - IN: <loadBalancer> # optional - IN: <any job or resource> # optional on_success: # optional - NOTIFY: <notification resource name> on_failure: # optional - NOTIFY: <notification resource name> on_cancel: # optional - NOTIFY: <notification resource name> always: # optional - NOTIFY: <notification resource name>
name-- should be an easy to remember text string
type-- is set to
dependencyMode-- Optional. This may be set to
chrono. For detailed explanation, read about job triggering mechanisms
steps-- is an object which contains specific instructions to run this job
IN-- You need at least one
loadBalancerresource as an input. Multiple
loadBalancerresources may be listed as inputs. Currently we only support
loadBalancerresource on GKE or Kubernetes services. If you need other entities please let us know.
- loadBalancer -- If a
loadBalanceris provided, the
provisionjob will attempt to create a loadBalancer based on the integration associated with the resource.
- loadBalancer -- If a
- Any other job or resource will only participate in triggering the
provisionjob, but not in of the processing of it.
alwaysare used to send notifications for those events. You need to provide a notification resource pointing to the provider like Slack, Email, IRC, Hipchat, etc.
The jobs section of the anatomy of shippable.yml page contains additional descriptions of these tags.
provisionjobs are managed jobs, free-form scripting is not allowed.
A new version of the
provisionjob is created every time it is executed. Since the job executions are versioned, it is easy to Replay an old version to trigger your Assembly Line with the old settings. However, you should only do so if you understand the impact to your Assembly Lines.