Skip to content

Ray values#

Values under ray configure the KubeRay operator, which runs the Ray clusters behind Ray jobs and notebooks.

Generated from the Hopsworks Helm chart 5.1.0 (Hopsworks 5.1.0).

Deployed according to the first of these values that is set: global._hopsworks.ray.enabled, global._hopsworks.full_platform.

Upstream charts

  • Values under ray.kuberay-operator go to kuberay-operator 1.4.0 from https://ray-project.github.io/kuberay-helm/.

Only the values Hopsworks sets under ray.kuberay-operator are listed on this page. Any other value of the chart can be set there too; the link opens its documentation for the version Hopsworks pins.

Defaults as YAML
ray:
  kuberay-operator:
    batchScheduler:
      enabled: false
      name: ''
    crNamespacedRbacEnable: true
    env: null
    featureGates:
    - enabled: false
      name: RayClusterStatusConditions
    fullnameOverride: kuberay-operator
    image:
      pullPolicy: IfNotPresent
      repository: docker.hops.works/hopsworks/kuberay-operator
      tag: 1.4.0-h1
    leaderElectionEnabled: true
    livenessProbe:
      failureThreshold: 5
      initialDelaySeconds: 10
      periodSeconds: 5
    logging:
      baseDir: ''
      fileEncoder: ''
      fileName: ''
      stdoutEncoder: ''
    nameOverride: kuberay-operator
    podSecurityContext: {}
    rbacEnable: true
    readinessProbe:
      failureThreshold: 5
      initialDelaySeconds: 10
      periodSeconds: 5
    resources:
      limits:
        cpu: 100m
        memory: 512Mi
    securityContext:
      allowPrivilegeEscalation: false
      capabilities:
        drop:
        - ALL
      readOnlyRootFilesystem: true
      runAsNonRoot: true
      seccompProfile:
        type: RuntimeDefault
    service:
      port: 8080
      type: ClusterIP
    serviceAccount:
      create: true
      name: kuberay-operator
    singleNamespaceInstall: false
ray #
Type object, default {}. override ray values
ray.kuberay-operator #

Type object, passed to the kuberay-operator 1.4.0 chart, whose other values are documented there. override kuberay-operator values

Default
batchScheduler:
  enabled: false
  name: ''
crNamespacedRbacEnable: true
env: null
featureGates:
- enabled: false
  name: RayClusterStatusConditions
fullnameOverride: kuberay-operator
image:
  pullPolicy: IfNotPresent
  repository: docker.hops.works/hopsworks/kuberay-operator
  tag: 1.4.0-h1
leaderElectionEnabled: true
livenessProbe:
  failureThreshold: 5
  initialDelaySeconds: 10
  periodSeconds: 5
logging:
  baseDir: ''
  fileEncoder: ''
  fileName: ''
  stdoutEncoder: ''
nameOverride: kuberay-operator
podSecurityContext: {}
rbacEnable: true
readinessProbe:
  failureThreshold: 5
  initialDelaySeconds: 10
  periodSeconds: 5
resources:
  limits:
    cpu: 100m
    memory: 512Mi
securityContext:
  allowPrivilegeEscalation: false
  capabilities:
    drop:
    - ALL
  readOnlyRootFilesystem: true
  runAsNonRoot: true
  seccompProfile:
    type: RuntimeDefault
service:
  port: 8080
  type: ClusterIP
serviceAccount:
  create: true
  name: kuberay-operator
singleNamespaceInstall: false