The arkouda-udp-locale Helm chart deploys 1..n arkouda-udp-locale docker containers that, together with the arkouda-udp-server bootstrap container, compose the Arkouda-on-Kubernetes deployment. The arkouda-udp-locale Helm chart is deployed first and, once all of the arkouda-udp-locale pods are running, the arkouda-udp-server Helm chart is deployed. The arkouda-udp-server container uses ssh to establish a GASNET/UDP-managed Arkouda multi-locale instance.
The arkouda-udp-locale Helm deployment is configured within the values.yaml file.
The releaseVersion parameter (Arkouda tag) and imagePullPolicy are set at the top of the Pod Settings section.
The resource request and limit parameters are specified in the resources element of the Pod Settings section. Note: the resource requests and limits parameters are the same because the compute resources allocated to Chapel processes is static.
resources:
limits:
cpu: 1000m
memory: 2024Mi
requests:
cpu: 1000m
memory: 2024Mi
The locale configuration section sets the number of arkouda-locale containers to startup along with other parameters as shown below:
locale:
numLocales: # number of arkouda-udp-locale pods
name: # Kubernetes app name used by arkouda-udp-server for pod discovery
threadsPerLocale: # number of cpu cores assigned to each Arkouda locale
The persistence section configures the container and host paths that, if persistence is enabled, enables users to write out Arkouda arrays to files:
persistence:
enabled: false
containerPath: /arkouda-files # container directory for reading/writing Arkouda files
hostPath: /mnt/data/arkouda-files # host directory for reading/writing Arkouda files
The name and the uid for the user running Arkouda if user-specific Arkouda is enabled. This setting is important if users wish to write Arkouda arrays out to Parquet or HDF5 as directory permissions require.
user:
enabled: # indicates whether to run Arkouda as a specified user, defaults to false
name: # name of user running arkouda and CN for corresponding secret for rolebindings
uid: # uid of user running Arkouda
The name and gid corresponding the user Arkouda is running as. The gid is normally used to enable writing Arkouda files to common-use directories:
group:
enabled: # indicates whether to run Arkouda as a specified user with corresponding group, defaults to false
name: # name of group user needs to configured for to execute host commands
gid: # gid of group user needs to configured for to execute host commands
The name of the SSH cert pair used to launch Arkouda-on-Kubernetes via the Chapel UDP launcher is specified in the secrets.ssh parameter:
secrets:
ssh: # name of ssh secret used to launch Arkouda locales
helm install -n arkouda arkouda-locale arkouda-udp-locale/