Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

UrbanCode Deploy Agent - Helm Chart


UrbanCode Deploy Agent is a tool for automating application deployments through your environments. It is designed to facilitate rapid feedback and continuous delivery in agile development while providing the audit trails, versioning and approvals needed in production.

Chart Details

  • This chart deploys a single instance of the UrbanCode Deploy agent that may be scaled to multiple instances.
  • The Persistent Volume access modes ReadWriteOnce (RWO) and ReadWriteMany (RWX) are both supported for use with IBM UrbanCode Deploy agent. However, ReadWriteMany is required to successfully scale to more than one replica/instance of the agent.
  • Includes a StatefulSet workload object


  1. Kubernetes 1.16.0+; kubectl and oc CLI; Helm 3;
  1. Accessing the container Image - The UrbanCode Deploy agent image is accessed via the IBM Entitled Registry.

    • Log in to MyIBM Container Software Library with the IBMid and password that are associated with the entitled software.
    • In the Entitlement keys section, select Copy key to copy the entitlement key to the clipboard.
    • An imagePullSecret must be created to be able to authenticate and pull images from the Entitled Registry. Once this secret has been created you will specify the secret name as the value for the image.secret parameter in the values.yaml you provide to 'helm install ...'. Note that secrets are namespace scoped, so they must be created in every namespace you plan to install UrbanCode Deploy agent into. Following is an example command to create an imagePullSecret named 'entitledregistry-secret'.
oc create secret docker-registry entitledregistry-secret --docker-username=cp --docker-password=<EntitlementKey>
  1. The agent must have an UrbanCode Deploy server or relay to connect to.

  2. Secret - A Kubernetes Secret object must be created to store the password for all keystores used by the product. The name of the secret you create must be specified in the property '' in your values.yaml.

  • Through the oc/kubectl CLI, create a Secret object in the target namespace. Generate the base64 encoded value for the password for all keystores used by the product.
echo -n 'MyKeystorePassword' | base64
  • Create a file named secret.yaml with the following contents, using your Helm Relese name and base64 encoded values.
apiVersion: v1
kind: Secret
  name: ucda-secrets
type: Opaque
  keystorepassword: TXlLZXlzdG9yZVBhc3N3b3Jk
  • Create the Secret using oc apply
oc apply -f ./secret.yaml
  • Delete or shred the secret.yaml file.
  1. A PersistentVolume that will hold the conf directory for the UrbanCode Deploy agent is required. If your cluster supports dynamic volume provisioning you will not need to create a PersistentVolume (PV) or PersistentVolumeClaim (PVC) before installing this chart. If your cluster does not support dynamic volume provisioning, you will need to either ensure a PV is available or you will need to create one before installing this chart. You can optionally create the PVC to bind it to a specific PV, or you can let the chart create a PVC and bind to any available PV that meets the required size and storage class. Sample YAML to create the PV and PVC are provided below.
apiVersion: v1
kind: PersistentVolume
  name: ucda-conf-vol
    volume: ucda-conf-vol
    storage: 10Mi
    - ReadWriteOnce
    path: /volume1/k8/ucda-conf
kind: PersistentVolumeClaim
apiVersion: v1
  name: ucda-conf-volc
  storageClassName: ""
    - "ReadWriteOnce"
      storage: 10Mi
      volume: ucda-conf-vol
  • The following storage options have been tested with IBM UrbanCode Deploy

    • IBM Block Storage supports the ReadWriteOnce access mode. ReadWriteMany is not supported.

    • IBM File Storage supports ReadWriteMany which is required for multiple instances of the UrbanCode Deploy agent.

  • IBM UrbanCode Deploy requires non-root access to persistent storage. When using IBM File Storage you need to either use the IBM provided “gid” File storage class with default group ID 65531 or create your own customized storage class to specify a different group ID. Please follow the instructions at for more details.

  1. If a route or ingress is used to access the WSS port of the UrbanCode Deploy server from an UrbanCode Deploy agent, then port 443 should be specified along with the configured URL to access the proper service port defined for the UrbanCode Deploy Server.

PodSecurityPolicy Requirements

If you are running on OpenShift, skip this section and continue to the SecurityContextConstraints Requirements section below.

This chart requires a PodSecurityPolicy to be bound to the target namespace prior to installation. Choose either a predefined PodSecurityPolicy or have your cluster administrator create a custom PodSecurityPolicy for you.

The predefined PodSecurityPolicy named ibm-restricted-psp has been verified for this chart, if your target namespace is bound to this PodSecurityPolicy you can proceed to install the chart.

  • Custom PodSecurityPolicy definition:
    apiVersion: extensions/v1beta1
    kind: PodSecurityPolicy
      annotations: "This policy is based on the most restrictive policy,
        requiring pods to run with a non-root UID, and preventing pods from accessing the host." docker/default docker/default
      name: ibm-ucd-prod-psp
      allowPrivilegeEscalation: false
      - '*'
        - max: 65535
          min: 1
        rule: MustRunAs
      hostNetwork: false
      hostPID: false
      hostIPC: false
      - ALL
        rule: MustRunAsNonRoot
        rule: RunAsAny
        - max: 65535
          min: 1
        rule: MustRunAs
      - configMap
      - emptyDir
      - projected
      - secret
      - downwardAPI
      - persistentVolumeClaim

SecurityContextConstraints Requirements

This chart requires a SecurityContextConstraints to be bound to the target namespace prior to installation. The default SecurityContextConstraints named restricted has been verified for this chart, if your target namespace is bound to this SecurityContextConstraints resource you can proceed to install the chart.

  • Custom SecurityContextConstraints definition:
kind: SecurityContextConstraints
allowHostDirVolumePlugin: false
allowHostIPC: false
allowHostNetwork: false
allowHostPID: false
allowHostPorts: false
allowPrivilegeEscalation: true
allowPrivilegedContainer: false
allowedCapabilities: null
defaultAddCapabilities: null
  type: MustRunAs
  annotations: restricted denies access to all host features and requires
      pods to be run with a UID, and SELinux context that are allocated to the namespace.  This
      is the most restrictive SCC and it is used by default for authenticated users.
  name: restricted
priority: null
readOnlyRootFilesystem: false
  type: MustRunAsRange
  type: MustRunAs
  type: RunAsAny
users: []
- configMap
- downwardAPI
- emptyDir
- persistentVolumeClaim
- projected
- secret

Resources Required

  • 200MB of RAM
  • 50 millicores CPU

Installing the Chart

Add the IBM helm chart repository to the local client.

$ helm repo add ibm-helm

Get a copy of the values.yaml file from the helm chart so you can update it with values used by the install.

$ helm inspect values ibm-helm/ibm-ucda-prod > myvalues.yaml

Edit the file myvalues.yaml to specify the parameter values to use when installing the UCD agent instance. The configuration section lists the parameter values that can be set.

To install the chart into namespace 'ucdtest' with the release name my-ucda-release and use the values from myvalues.yaml:

$ helm install my-ucda-release ibm-helm/ibm-ucda-prod --namespace ucdtest --values myvalues.yaml

Tip: List all releases using helm list.

Verifying the Chart

Check the Resources->Agents page of the UrbanCode Deploy server UI to verify the agent has connected successfully.

Uninstalling the Chart

To uninstall/delete the my-ucda-release deployment:

$ helm delete my-ucda-release

The command removes all the Kubernetes components associated with the chart and deletes the release.



The Helm chart has the following values that can be overriden using the --set parameter or specified via -f my_values.yaml.

Common Parameters
Qualifier Parameter Definition Allowed Value
version UrbanCode Deploy agent product version
replicas agent Number of UCD agent replicas Non-zero number of replicas. Defaults to 1
image pullPolicy Image Pull Policy Always, Never, or IfNotPresent. Defaults to Always
secret An image pull secret used to authenticate with the image registry Empty (default) if no authentication is required to access the image registry.
license accept Set to true to indicate you have read and agree to license agreements : false
persistence enabled Determines if persistent storage will be used to hold the UCD agent conf directory contents. This should always be true to preserve agent data on container restarts. Default value "true"
useDynamicProvisioning Set to "true" if the cluster supports dynamic storage provisoning Default value "true"
fsGroup The group ID to use to access persistent volumes Default value "1001"
confVolume name The base name used when the Persistent Volume and/or Persistent Volume Claim for the UCD agent conf directory is created by the chart. Default value is "conf"
existingClaimName The name of an existing Persistent Volume Claim that references the Persistent Volume that will be used to hold the UCD agent conf directory.
storageClassName The name of the storage class to use when persistence.useDynamicProvisioning is set to "true".
size Size of the volume to hold the UCD agent conf directory
accessMode Persistent storage access mode for the conf directory persistent volume. ReadWriteOnce
relayUri Agent Relay Proxy URI if the agent is connecting to a relay. If multiple relays are specified, separate them with commas. For example, random:(http://relay1:20080,http://relay2:20080)
codestationUrl Agent Relay Codestation URL. If multiple relays are specified, separate them with commas. For example, random:(http://relay1:20081,http://relay2:20081)
serverUri UCD server URI. If multiple servers are specified, separate them with commas. For example, random:(wss://,wss://
secret name Kubernetes secret which defines password to use when creating keystores.
agentTeams Teams to add this agent to when it connects to the UCD server.Format is :. Multiple team specifications are separated with a comma.
userUtils existingClaimName Name of existing Persistent Volume Claim that refers to Persistent Volume that contains executables for the agent process to execute as part of deployment processes.
executablesPath Relative pathname to the directory containing the user provided executable(s). Comma separate multiple directory paths. Default is '.', the top-level directory of the PV.
resources constraints.enabled Specifies whether the resource constraints specified in this helm chart are enabled. false (default) or true
limits.cpu Describes the maximum amount of CPU allowed Default is 2000m. See Kubernetes - meaning of CPU
limits.memory Describes the maximum amount of memory allowed Default is 2Gi. See Kubernetes - meaning of Memory
requests.cpu Describes the minimum amount of CPU required - if not specified will default to limit (if specified) or otherwise implementation-defined value. Default is 50m. See Kubernetes - meaning of CPU
requests.memory Describes the minimum amount of memory required If not specified, the memory amount will default to the limit (if specified) or the implementation-defined value Default is 200Mi. See Kubernetes - meaning of Memory


To increase or decrease the number of UrbanCode Deploy Agent instances issue the following command:

$ oc scale --replicas=2 statefulset/releaseName-ibm-ucda-prod

User defined utilities to run in UrbanCode Deploy Agent container

Users can extend the tools the agent can execute without having to modify the image. The user can provide a Persistent Volume Claim(PVC) in the values.yaml file. This PVC would refer to a Persistent Volume(PV) the user has created and load the executables they want the agent to run. See the userUtils.existingClaimName and userUtils.executablesPath in the "Configuration" on how to provide user defined utilities.


See the Prerequisites section of this page for storage information.