Managing ECDs with Kubectl or Helm (3.1)

Creating ECDs

Creating an ECD is done by submitting an ECDeployment resource creation request to Kubernetes. Below are a few examples showing how this can be done. These examples use kubectl as the tool to create the ECDs. The same resources can be created using the EC Deployment Web Interface(3.0). This UI can also be used as a tool to configure the ECD YAML resource and then manage it using Kubectl or Helm (see below).

Managing ECDs with Kubectl

Use this command to retrieve all the EC deployments that are in your installation:

kubectl get ecd -n <namespace>

Use this command to retrieve a specific EC deployment in your installation:

kubectl get ecd <deployment name> -n <namespace>

Use this command to describe a specific EC deployment in your installation:

kubectl describe ecd <deployment name> -n <namespace>

Use this command to allow an ECD to be enabled/disables based on the scheduling of the workflow group(s) within the ECD:

kubectl edit ecd <your ECD name>

and then set enableOnSchedule to true or false in the spec: section.

spec:

disabled: true

enableOnSchedule: true

Managing ECDs with Helm

ECD resources can easily be packaged into Helm charts to be able to orchestrate and parameterise them in CI/CD pipelines and using different Helm enabled tools.

An example to set up an empty EC through an Helm packaged ECD resource can be found here:

https://github.com/digitalroute/mz-example-workflows/tree/master/helm

Note that all configuration of the ECD spec goes into the values.yaml file.