Kubernetes installation

# Note: if you have multiple Deephaven installations you may want to preface the PV and PVC names
# with a prefix to differentiate it such as dev1, qa, uat, etc.
apiVersion: v1
kind: PersistentVolume
metadata:
  name: etcd-backup-snapshot-pv
spec:
  persistentVolumeReclaimPolicy: Retain
  accessModes:
    - ReadWriteMany
  capacity:
    storage: 20Gi
  mountOptions:
    - hard
    - nfsvers=4.1
  nfs:
    server: 10.122.10.43
    path: /exports/dhsystem/etcd-backup
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: etcd-backup-snapshot-pvc
spec:
  accessModes:
    - ReadWriteMany
  storageClassName: ''
  volumeName: etcd-backup-snapshot-pv
  resources:
    requests:
      storage: 20Gi

# deephaven-override-values.yaml

# ------------------------------------------------------------------------------------------------
# Mandatory Configuration Values:
# These values must be defined in order to deploy the Deephaven helm chart.
image:
  # This must be set to the image repository location to which you pushed your images.
  repositoryUrl: 'my-repo.dev/my-project/images/deephaven-install'

  # The tag with which the images were pushed to your repo. Note that you may opt to omit this in your
  # yaml file, and instead provide it on the command line as --set image.tag=1.20240517.344.
  # That would prevent using the incorrect tag in an old config file when performing a future upgrade to
  # a new Deephaven version.
  tag: '1.20240517.344'

# The hostname/DNS entry used for your Deephaven cluster. It must correspond with the TLS certificate
# created in an earlier step as the deephaven-tls secret.
envoyFrontProxyUrl: dh.yourdomain.com

nfs:
  # A short prefix prepended to pv and pvc names to distinguish them, if you have multiple environments.
  pvPrefix: 'dh-dev1'
  # If using the Deephaven nfs server created earlier, the server should be the CLUSTER-IP you see by
  # running kubectl get svc deephaven-nfs, e.g. 10.122.10.43
  server: '10.122.10.43'
  # If using the Deephaven nfs server there is no need to define the root. If you were to use your own
  # nfs server this would need to set to the path available to the system.
  root: '/exports/dhsystem'

etcd:
  # This is the secret containing the etcd root password that was generated when installing
  # etcd. It may not match the etcd release name you used earlier. Run the command 'kubectl get
  # secrets' and make sure your value is there.
  release: 'dh-etcd'

global:
  # This value should be set to a storage class in your environment with a provider that can
  # dynamically provision volumes. For example, this can be 'standard-rwo' for GKE environments,
  # 'gp2' for EKS, or managed-csi for AKS.
  storageClass: 'default'

# ------------------------------------------------------------------------------------------------
# Recommended Configuration Values:
# Strongly consider defining resource values for your use case, particularly memory settings.

# Resource sizes for Deephaven processes can be configured here. Note that only the default config
# for the log aggregator service (LAS) is shown here for brevity. You may add configs for these processes
# in addition to the las: aclwriter, authserver, configuration-server, controller, las, merge-server,
# query-server, tdcp, and webapi.
resources:
  las:
    binlogsSize: '20Gi'
    requests:
      cpu: '500m'
      memory: '4Gi'
      ephemeral-storage: '1Gi'
    limits:
      memory: '4Gi'
      ephemeral-storage: '1Gi'
    tailer:
      requests:
        cpu: '250m'
        memory: '2Gi'
        ephemeral-storage: '1Gi'
      limits:
        memory: '2Gi'
        ephemeral-storage: '1Gi'
  # Note that you do not need to provide all values shown above for the las. You can configure an
  # override only for controller.requests.cpu, for example. However, when setting memory it is
  # recommended that you set requests.memory and limits.memory to be identical, or pods may be
  # subject to eviction and OOMKilled errors.
  # This is an example configuration setting memory for the controller process at 4Gi and the
  # memory for the controller's tailer process to 2Gi, leaving other settings at their defaults.
  controller:
    requests:
      memory: '4Gi'
    limits:
      memory: '4Gi'
    tailer:
      requests:
        memory: '2Gi'
      limits:
        memory: '2Gi'

# Custom DIS process volume configuration. Set intradaySize and intradayUserSize to appropriate values for your
# target environment, or consult with Deephaven to evaluate your use case and make a recommendation. 10Gi default.
dis:
  intradaySize: 10Gi
  intradayUserSize: 10Gi

# ------------------------------------------------------------------------------------------------
# Optional Values:
# These values may be defined to override the Deephaven defaults. Note that this is an incomplete
# list of the values defined in the Deephaven chart, but it represents those values most likely to
# require changes. The full file with all chart configurations is in the helm distribution at
# deephaven-helm-1.20240517.344/helm/deephaven/values.yaml

# ALL OPTIONAL VALUES SHOWN ARE THE DEFAULTS AND CAN BE OMITTED UNLESS YOU ARE CHANGING THEM.

# You can add annotations for the envoy load balancer that is the front-end to the Deephaven application
# by putting the values here under envoy.serviceAnnotations. There is no default here, and values will
# vary by provider. Note that if none are provided, the default service type of 'LoadBalancer' may
# allocate an externally accessible IP address. The values in comments below are examples only - please
# consult your provider's documentation for further information.
envoy:
  serviceAnnotations:
#    service.beta.kubernetes.io/aws-load-balancer-subnets: "dh-ice2-bastion"
#    service.beta.kubernetes.io/aws-load-balancer-type: "nlb"
#    service.beta.kubernetes.io/aws-load-balancer-nlb-target-type: "instance"
#    service.beta.kubernetes.io/aws-load-balancer-eip-allocations: "eipalloc-0a4ac88c475cf2d5b"
#    service.beta.kubernetes.io/aws-load-balancer-scheme: internet-facing

# Set to 'Always' for k8s to always pull the image when starting a container.
imagePullPolicy: 'IfNotPresent'

tailers:
  # How many minutes elapse since file's last modified time before a binlog is deleted in tailer containers.
  fileCleanupDeleteAfterMinutes: 240

# If you wish to use cert-manager for intra-cluster TLS process communication please contact a Deephaven representative.
certmgr:
  enabled: false

management:
  # Add the etcd root password as an env var named ETCD_ROOT_PASSWORD in the management-shell pod.
  addRootEtcdPasswordEnvVar: true

# If you are pulling source code from git to create a persistent query, set this to true.
controller:
  gitCreateVolume: false