> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Slurm parameter reference

> Complete parameter reference for the Slurm Helm chart, including accounting, compute, and deployment settings

![Version: 0.1.0](https://img.shields.io/badge/Version-0.1.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square)

## Requirements

| Repository                               | Name        | Version |
| ---------------------------------------- | ----------- | ------- |
| file://../library                        | library     | 0.1.0   |
| file://../slurm-login                    | slurm-login | 0.1.0   |
| oci://registry-1.docker.io/bitnamicharts | mysql       | 9.19.1  |

## Parameters

<table>
  <thead>
    <th style={{ width: '45%', textAlign: 'left' }}>Key & Description</th>
    <th style={{ textAlign: 'left' }}>Type</th>
    <th style={{ textAlign: 'left' }}>Default</th>
  </thead>

  <tbody>
    <tr>
      <td id="accounting--annotations">
        <b>accounting.annotations</b><br />
        Additional annotations for accounting resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--ArchiveEvents">
        <b>accounting.config.ArchiveEvents</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "yes"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--ArchiveJobs">
        <b>accounting.config.ArchiveJobs</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "yes"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--ArchiveResvs">
        <b>accounting.config.ArchiveResvs</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "yes"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--ArchiveSteps">
        <b>accounting.config.ArchiveSteps</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "no"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--ArchiveSuspend">
        <b>accounting.config.ArchiveSuspend</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "no"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--ArchiveTXN">
        <b>accounting.config.ArchiveTXN</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "no"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--ArchiveUsage">
        <b>accounting.config.ArchiveUsage</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "no"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--AuthAltParameters[0]">
        <b>accounting.config.AuthAltParameters\[0]</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "jwt_key=/etc/jwt/jwt.key"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--AuthAltTypes">
        <b>accounting.config.AuthAltTypes</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "auth/jwt"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--AuthType">
        <b>accounting.config.AuthType</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "auth/munge"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--DbdPort">
        <b>accounting.config.DbdPort</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        6819
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--DebugLevel">
        <b>accounting.config.DebugLevel</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "verbose"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--LogFile">
        <b>accounting.config.LogFile</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/dev/null"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--PidFile">
        <b>accounting.config.PidFile</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/var/run/slurmdbd.pid"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--PurgeEventAfter">
        <b>accounting.config.PurgeEventAfter</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "1month"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--PurgeJobAfter">
        <b>accounting.config.PurgeJobAfter</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "12month"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--PurgeResvAfter">
        <b>accounting.config.PurgeResvAfter</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "1month"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--PurgeStepAfter">
        <b>accounting.config.PurgeStepAfter</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "1month"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--PurgeSuspendAfter">
        <b>accounting.config.PurgeSuspendAfter</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "1month"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--PurgeTXNAfter">
        <b>accounting.config.PurgeTXNAfter</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "12month"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--PurgeUsageAfter">
        <b>accounting.config.PurgeUsageAfter</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "24month"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--SlurmUser">
        <b>accounting.config.SlurmUser</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "slurm"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--StoragePort">
        <b>accounting.config.StoragePort</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        3306
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--config--StorageType">
        <b>accounting.config.StorageType</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "accounting_storage/mysql"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--enabled">
        <b>accounting.enabled</b><br />
        Enable the accounting.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--external--enabled">
        <b>accounting.external.enabled</b><br />
        Enable the external accounting, instead of deploying an internal accounting instance. This configuration also requires the underlying database for <code>slurmdbd</code> to be managed externally.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--external--host">
        <b>accounting.external.host</b><br />
        The host of the external accounting instance: IP or hostname.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--external--port">
        <b>accounting.external.port</b><br />
        The port of the external accounting instance.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--external--user">
        <b>accounting.external.user</b><br />
        The user to use to authenticate to the external accounting instance.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--externalDB--enabled">
        <b>accounting.externalDB.enabled</b><br />
        Configure Slurm Accounting (<code>slurmdbd</code>) with an external database.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--externalDB--existingSecret">
        <b>accounting.externalDB.existingSecret</b><br />
        Specify the name of the Kubernetes Secret that contains the password used by <code>slurmdbd</code> to access the Slurm accounting database. This Secret <strong>must</strong> contain a data key named <code>db-password</code> whose value is the actual database password. <strong>Important</strong>: The password value stored in the Secret <strong>cannot</strong> contain the hash (<code>#</code>) character.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--externalDB--storageHost">
        <b>accounting.externalDB.storageHost</b><br />
        The hostname of the server where the database resides.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--externalDB--storageLoc">
        <b>accounting.externalDB.storageLoc</b><br />
        The name of the database used to store Slurm accounting records. Defaults to "slurm\_acct\_db".
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "slurm_acct_db"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--externalDB--storageUser">
        <b>accounting.externalDB.storageUser</b><br />
        The username <code>slurmdbd</code> uses for authentication and storing job accounting data.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--image">
        <b>accounting.image</b><br />
        The image to use for slurmdbd deployment.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        name: controller
        repository:
        tag:

        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--labels">
        <b>accounting.labels</b><br />
        Additional labels for accounting resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--livenessProbe">
        <b>accounting.livenessProbe</b><br />
        The liveness probe for the slurmdbd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        exec:
            command:
                - sacctmgr
                - ping
        initialDelaySeconds: 15
        periodSeconds: 10
        failureThreshold: 5
        successThreshold: 1
        timeoutSeconds: 60

        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--priorityClassName">
        <b>accounting.priorityClassName</b><br />
        The priority class name for the accounting pod.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sunk-control-plane"
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--readinessProbe">
        <b>accounting.readinessProbe</b><br />
        The readiness probe for the slurmdbd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        exec:
            command:
                - sacctmgr
                - ping
        initialDelaySeconds: 15
        periodSeconds: 10
        failureThreshold: 5
        successThreshold: 1
        timeoutSeconds: 60

        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--replicas">
        <b>accounting.replicas</b><br />
        The number of replicas of the accounting instance to run.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        1
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--resources">
        <b>accounting.resources</b><br />
        Resources for the accounting container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 64Gi
        requests:
            cpu: 16
            memory: 64Gi

        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--securityContext--runAsGroup">
        <b>accounting.securityContext.runAsGroup</b><br />
        The group to run as, must match the slurm GID from the container image.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        401
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--securityContext--runAsUser">
        <b>accounting.securityContext.runAsUser</b><br />
        The user to run as, must match the slurm UID from the container image.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        401
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--startupProbe">
        <b>accounting.startupProbe</b><br />
        The startup probe for the slurmdbd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--terminationGracePeriodSeconds">
        <b>accounting.terminationGracePeriodSeconds</b><br />
        The termination grace period for the accounting pod.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        30
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--useExistingSecret">
        <b>accounting.useExistingSecret</b><br />
        Use an existing secret for the accounting instance instead of creating. <br /> The secret name is the same as the mysql.auth.existingSecret.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--volumeMounts">
        <b>accounting.volumeMounts</b><br />
        Additional volume mounts to apply to the accounting pod.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="accounting--volumes">
        <b>accounting.volumes</b><br />
        Additional volumes to mount to the accounting pod.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--annotations">
        <b>cleanupCompleting.annotations</b><br />
        Additional annotations for cleanup-completing Job resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--cronJobSchedule">
        <b>cleanupCompleting.cronJobSchedule</b><br />
        The schedule for the cleanup-completing CronJob. It should be formatted according to the cron convention. Default runs every minute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "* * * * *"
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--deleteInvalidNodes">
        <b>cleanupCompleting.deleteInvalidNodes</b><br />
        Enable deletion of nodes that are in INVALID\_REG state after downing them. This allows nodes to cleanly re-register with Slurm.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--dryRun">
        <b>cleanupCompleting.dryRun</b><br />
        Enable dry run mode - shows what would be done without actually downing nodes.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--enabled">
        <b>cleanupCompleting.enabled</b><br />
        Enable cleanup of nodes with jobs stuck in COMPLETING state.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--labels">
        <b>cleanupCompleting.labels</b><br />
        Additional labels for cleanup-completing Job resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--nodeSelector--affinity">
        <b>cleanupCompleting.nodeSelector.affinity</b><br />
        The affinity for the cleanup-completing Job. This overrides the value of <a href="https://docs.coreweave.com/products/sunk/reference/slurm-parameters#global--nodeSelector--affinity"> <code>global.nodeSelector.affinity</code></a>.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--priorityClassName">
        <b>cleanupCompleting.priorityClassName</b><br />
        The priority class name for the cleanup-completing Job pod.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sunk-control-plane"
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--resources">
        <b>cleanupCompleting.resources</b><br />
        Resources for the cleanup-completing Job container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 256Mi
        requests:
            cpu: 100m
            memory: 64Mi

        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--timeoutSeconds">
        <b>cleanupCompleting.timeoutSeconds</b><br />
        Timeout in seconds for jobs in COMPLETING state before downing nodes. Jobs that have been completing longer than this threshold will trigger node downing (if no other jobs are present on the node). If not specified, defaults to 2x KillWait from slurm.conf.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--tolerations">
        <b>cleanupCompleting.tolerations</b><br />
        The tolerations for the cleanup-completing Job
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="cleanupCompleting--verbose">
        <b>cleanupCompleting.verbose</b><br />
        Enable verbose logging for debugging.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--annotations">
        <b>compute.annotations</b><br />
        Additional annotations for compute services only. Use `compute.nodes.custom-definition.annotations` to add annotations to specific node definitions instead.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--autoPartition--config">
        <b>compute.autoPartition.config</b><br />
        The following are intended for the customer to update. These values will be applied to each auto-generated partition. The partition name will be the same as the node definition name.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          config:
            OverSubscribe: "YES"
            MaxTime: "12:00:00"
            QoS: "NORMAL"
          ```
        </Accordion>
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--autoPartition--enabled">
        <b>compute.autoPartition.enabled</b><br />
        Enable the auto partition.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--cacheDropper--enabled">
        <b>compute.cacheDropper.enabled</b><br />
        An option to enable or disable the cache-dropper sidecar container across all slurmd pods.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--cacheDropper--resources">
        <b>compute.cacheDropper.resources</b><br />
        Resources for the cache-dropper sidecar container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 32Mi
        requests:
            cpu: 500m
            memory: 32Mi

        ```
      </td>
    </tr>

    <tr>
      <td id="compute--epilogConfigMap">
        <b>compute.epilogConfigMap</b><br />
        The name or list of configmap names containing epilog scripts
      </td>

      <td>string | list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--externalClusterName">
        <b>compute.externalClusterName</b><br />
        The name of an external cluster to join. <br /> This is used when control plane is deployed separately.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--generateTopology">
        <b>compute.generateTopology</b><br />
        Enable topology generation for the compute nodes in the cluster.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--gpusd">
        <b>compute.gpusd</b><br />
        Configuration for GPUSD (GPU Straggler Detection) metrics collection.
      </td>

      <td>object</td>
      <td>See individual settings below.</td>
    </tr>

    <tr>
      <td id="compute--gpusd--enabled">
        <b>compute.gpusd.enabled</b><br />
        Enable GPUSD package installation, metrics collection, and VMPodScrape resource.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--gpusd--version">
        <b>compute.gpusd.version</b><br />
        GPUSD version to install.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "1.0.0"
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--initialState">
        <b>compute.initialState</b><br />
        The initial state for the nodes when they join the slurm cluster. <br /> This is generally <code>drain</code> or <code>idle</code>. May also be set per node definition.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "idle"
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--initialStateReason">
        <b>compute.initialStateReason</b><br />
        The reason for setting the initial state of the nodes to down, drained, or fail. <br /> May also be set per node definition.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "Node added to the cluster for the first time"
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--labels">
        <b>compute.labels</b><br />
        Additional labels for compute services only. Use `compute.nodes.custom-definition.labels` to add labels to specific node definitions instead.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--livenessProbe">
        <b>compute.livenessProbe</b><br />
        The liveness probe for the compute slurmd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--maxUnavailable">
        <b>compute.maxUnavailable</b><br />
        The maximum unavailability of the compute nodes during a rolling update. <br /> Can be percentage or a number.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "10%"
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--nodes">
        <b>compute.nodes</b><br />
        Multiple node definitions can be declared, but only one may be <code>enabled: true</code>. Node definitions can reference other definitions to include or overlay values. See the example below or the <a href="https://docs.coreweave.com/products/sunk/deploy_sunk/configure-compute-nodes">Compute Node Definitions</a> documentation for more details.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          compute:
            nodes:
              # A custom definition to be referenced by other nodes
              custom-dns:
                dnsPolicy: "None"
                dnsConfig:
                  nameservers:
                    - 127.0.0.1
              # A simple CPU-only Node that uses the custom-dns definition above
              simple-cpu:
                enabled: true
                # Partition creation for the nodeset. The nodeset will still be assigned to the `all`
                # partition if creation is disabled
                createPartition: true
                # The following Partition configurations are for the customer to update.
                # These values will be applied to the autogenerated partition and will override the defaults.
                partitionConfig:
                  OverSubscribe: "YES"
                  MaxTime: "12:00:00"
                  QoS: "NORMAL"
                replicas: 1
                definitions:
                  # Use the custom-dns definition
                  - custom-dns
                staticFeatures:
                  - cpu
                dynamicFeatures:
                  node.coreweave.cloud/class: {}
                image:
                  name: controller-extras
                gresGpu: null
                config:
                  weight: 1
                # Create a small node with 1cpu and 1g memory
                resources:
                  limits:
                    memory: 1Gi
                    cpu: 1
                  requests:
                    memory: 1Gi
                    cpu: 1
                tolerations:
                  - key: is_cpu_compute
                    operator: Exists
                volumeMounts:
                  - name: ramtmp
                    mountPath: /tmp
                volumes:
                  - name: ramtmp
                    emptyDir:
                      medium: Memory
                affinity:
                  nodeAffinity:
                    requiredDuringSchedulingIgnoredDuringExecution:
                      nodeSelectorTerms:
                        - matchExpressions:
                            - key: kubernetes.io/os
                              operator: In
                              values:
                                - linux
          ```
        </Accordion>
      </td>

      <td>object</td>
      <td>See <a href="https://docs.coreweave.com/products/sunk/deploy_sunk/configure-compute-nodes">Compute Node Definitions</a>.</td>
    </tr>

    <tr>
      <td id="compute--partitionBaseConfig">
        <b>compute.partitionBaseConfig</b><br />
        Default configuration for partitions in the cluster. These values can be overridden per partition in the autoPartition section.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          partitionBaseConfig:
            MaxTime: "INFINITE"
            State: "UP"
          ```
        </Accordion>
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {
          "MaxTime": "INFINITE",
          "State": "UP"
        }
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--partitions">
        <b>compute.partitions</b><br />
        Partitions to add to the cluster. The key is the partition name and the value is the partition configuration.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        all: Nodes=ALL Default=YES

        ```
      </td>
    </tr>

    <tr>
      <td id="compute--plugstackConfig">
        <b>compute.plugstackConfig</b><br />
        Additional plug-in stack configuration items for <code>plugstack.conf</code> file config. Config Options: [https://slurm.schedmd.com/spank.html#SECTION\_CONFIGURATION](https://slurm.schedmd.com/spank.html#SECTION_CONFIGURATION)
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--ports">
        <b>compute.ports</b><br />
        Additional ports to expose on the compute nodes.

        <Accordion title="Example: NCCL Plugin ports">
          ```yaml theme={"system"}
          ports:
            - containerPort: 10400
              protocol: TCP
            - containerPort: 10401
              protocol: TCP
            - containerPort: 10402
              protocol: TCP
            - containerPort: 10403
              protocol: TCP
            - containerPort: 10404
              protocol: TCP
            - containerPort: 10405
              protocol: TCP
            - containerPort: 10406
              protocol: TCP
            - containerPort: 10407
              protocol: TCP
          ```
        </Accordion>
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--prologConfigMap">
        <b>compute.prologConfigMap</b><br />
        The name or list of configmap names containing prolog scripts
      </td>

      <td>string | list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--pyxis--appArmorProfile">
        <b>compute.pyxis.appArmorProfile</b><br />
        The AppArmor profile to use for the pyxis container.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "localhost/enroot"
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--pyxis--enabled">
        <b>compute.pyxis.enabled</b><br />
        Enable the pyxis container.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--pyxis--enrootConfig">
        <b>compute.pyxis.enrootConfig</b><br />
        Configuration options for enroot.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        ENROOT_RUNTIME_PATH: /run/enroot/user-$(id -u)
        ENROOT_CACHE_PATH: /opt/sunk/tmp/enroot-cache/user-$(id -u)
        ENROOT_DATA_PATH: /opt/sunk/tmp/enroot-data/user-$(id -u)
        # Enables <code>ENROOT_MOUNT_HOME</code> for the pyxis container to mount the home directory.
        ENROOT_MOUNT_HOME: y
        # Enables <code>ENROOT_REMAP_ROOT</code> for the pyxis container to remap the root user.
        ENROOT_REMAP_ROOT: y
        ENROOT_RESTRICT_DEV: n
        ENROOT_ROOTFS_WRITABLE: y

        ```
      </td>
    </tr>

    <tr>
      <td id="compute--pyxis--plugstackOptions">
        <b>compute.pyxis.plugstackOptions</b><br />
        Additional arguments for the pyxis plugin in <code>plugstack.conf</code> file config. Config Options: [https://github.com/NVIDIA/pyxis/wiki/Setup#slurm-plugstack-configuration](https://github.com/NVIDIA/pyxis/wiki/Setup#slurm-plugstack-configuration)
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        [
          "container_scope=global"
        ]
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--pyxis--podSecurityContext">
        <b>compute.pyxis.podSecurityContext</b><br />
        Security context for the pyxis container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {
          "seccompProfile": {
            "localhostProfile": "profiles/enroot",
            "type": "Localhost"
          }
        }
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--pyxis--podSecurityContext--seccompProfile">
        <b>compute.pyxis.podSecurityContext.seccompProfile</b><br />
        The seccomp profile to use for the pyxis container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {
          "localhostProfile": "profiles/enroot",
          "type": "Localhost"
        }
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--readinessProbe">
        <b>compute.readinessProbe</b><br />
        The readiness probe for the compute slurmd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        exec:
            command:
                - scontrol
                - show
                - slurmd
        failureThreshold: 3
        periodSeconds: 10
        successThreshold: 1
        timeoutSeconds: 5

        ```
      </td>
    </tr>

    <tr>
      <td id="compute--reservedMemory">
        <b>compute.reservedMemory</b><br />
        Reserved memory when calculating DefMemPerCPU config for slurm.conf
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "4Gi"
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--s6">
        <b>compute.s6</b><br />
        <strong>oneshot</strong> and <strong>longrun</strong> jobs are supported. See <a href="https://docs.coreweave.com/products/sunk/run_workloads/run-scripts-with-s6">Running Scripts with S6</a> for more information.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          s6:
            packages:
              type: oneshot
              timeoutUp: 0
              timeoutDown: 0
              script: |
                #!/usr/bin/env bash
                apt -y update
                apt -y install nginx
            nginx:
              type: longrun
              timeoutUp: 0
              timeoutDown: 0
              script: |
                #!/usr/bin/env bash
                nginx -g "daemon off;"
          ```
        </Accordion>
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--securityContext--capabilities--add">
        <b>compute.securityContext.capabilities.add</b><br />
        Add capabilities to the slurmd container. <br /> <code>"SYS\_ADMIN"</code> is required if using pyxis.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          compute:
            securityContext:
              capabilities:
                add: ["SYS_ADMIN"]
          ```
        </Accordion>
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        [
          "SYS_NICE",
          "SYS_ADMIN",
          "SYS_PTRACE",
          "SYSLOG"
        ]
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--ssh--enabled">
        <b>compute.ssh.enabled</b><br />
        Enable ssh to the compute nodes.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--startupProbe">
        <b>compute.startupProbe</b><br />
        The startup probe for the compute slurmd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--volumeMounts">
        <b>compute.volumeMounts</b><br />
        Additional volume mounts to add to all the compute pods, also added to login pods.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="compute--volumes">
        <b>compute.volumes</b><br />
        Additional volumes to mount to all the compute pods, also added to login pods.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="controlPlane--enabled">
        <b>controlPlane.enabled</b><br />
        Enable the Slurm control plane. <br /> Unless splitting the deployment this should be enabled.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--annotations">
        <b>controller.annotations</b><br />
        Additional annotations for controller resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--enabled">
        <b>controller.enabled</b><br />
        Enable the controller deployment <br /> This should be enabled unless more complicated deployment is required (splitting the deployment).
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--etcConfigMap">
        <b>controller.etcConfigMap</b><br />
        The ConfigMap(s) with keys mapping to files in <code>/etc/slurm</code> on the controller only. <br /> This ConfigMap <strong>must not</strong> contain: <ul> <li><code>slurm.conf</code></li> <li><code>plugstack.conf</code></li> <li><code>gres.conf</code></li> <li><code>cgroup.conf</code></li> <li><code>topology.conf</code></li> </ul>
      </td>

      <td>string | list</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--image">
        <b>controller.image</b><br />
        The image to use for the controller.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        name: controller
        repository:
        tag:

        ```
      </td>
    </tr>

    <tr>
      <td id="controller--labels">
        <b>controller.labels</b><br />
        Additional labels for controller resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--livenessProbe">
        <b>controller.livenessProbe</b><br />
        The liveness probe for the controller.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        exec:
            command:
                - scontrol
                - ping
        failureThreshold: 6
        initialDelaySeconds: 15
        periodSeconds: 10
        successThreshold: 1
        timeoutSeconds: 60

        ```
      </td>
    </tr>

    <tr>
      <td id="controller--priorityClassName">
        <b>controller.priorityClassName</b><br />
        The priority class name for the controller.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sunk-control-plane"
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--readinessProbe">
        <b>controller.readinessProbe</b><br />
        The readiness probe for the controller.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--replicas">
        <b>controller.replicas</b><br />
        The number of replicas of the controller to run, currently should be left at <code>1</code>.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        1
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--resources">
        <b>controller.resources</b><br />
        Resources for the controller container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 64Gi
        requests:
            cpu: 16
            memory: 64Gi

        ```
      </td>
    </tr>

    <tr>
      <td id="controller--securityContext--runAsGroup">
        <b>controller.securityContext.runAsGroup</b><br />
        The group to run as, must match the slurm GID from the container image.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        401
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--securityContext--runAsUser">
        <b>controller.securityContext.runAsUser</b><br />
        The user to run as, must match the slurm UID from the container image.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        401
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--startupProbe">
        <b>controller.startupProbe</b><br />
        The startup probe for the controller.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--stateVolume--size">
        <b>controller.stateVolume.size</b><br />
        The size of the persistent volume claim.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "32Gi"
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--stateVolume--storageClassName">
        <b>controller.stateVolume.storageClassName</b><br />
        The storage class name to use for the volume.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "shared-vast"
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--terminationGracePeriodSeconds">
        <b>controller.terminationGracePeriodSeconds</b><br />
        The termination grace period for the controller.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        30
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--volumeMounts">
        <b>controller.volumeMounts</b><br />
        Additional volume mounts to apply to the controller pod.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--volumes">
        <b>controller.volumes</b><br />
        Additional volumes to mount to the controller pod.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--watch--enabled">
        <b>controller.watch.enabled</b><br />
        Enable watching the Slurm configuration and triggering a reconfigure when there are changes.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--watch--interval">
        <b>controller.watch.interval</b><br />
        The interval in seconds to check for changes in the Slurm configuration.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        60
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--watch--livenessProbe">
        <b>controller.watch.livenessProbe</b><br />
        The liveness probe for the watch container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--watch--readinessProbe">
        <b>controller.watch.readinessProbe</b><br />
        The readiness probe for the watch container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="controller--watch--startupProbe">
        <b>controller.watch.startupProbe</b><br />
        The startup probe for the watch container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--debugLevel">
        <b>directoryService.debugLevel</b><br />
        A bit mask of what <a href="https://manpages.org/sssd/8">SSSD debug levels</a> to enable.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        0x01F0
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories">
        <b>directoryService.directories</b><br />
        The directory services to configure. Click to expand examples.

        <Accordion title="Google Secure LDAP">
          ```yaml theme={"system"}
          directories:
            - name: google-example.com
              enabled: true
              ldapUri: ldaps://ldap.google.com:636
              user:
                canary: user@google-example.com
              defaultShell: "/bin/bash"
              fallbackHomeDir: "/home/%u"
              overrideHomeDir: /mnt/nvme/home/%u
              ldapsCert: google-ldaps-cert
              schema: rfc2307bis
          ```
        </Accordion>

        <Accordion title="CoreWeave LDAP">
          ```yaml theme={"system"}
          directories:
            - name: coreweave.cloud
              enabled: true
              ldapUri: ldap://openldap
              user:
                bindDn: cn=admin,dc=coreweave,dc=cloud
                searchBase: dc=coreweave,dc=cloud
                existingSecret: bind-user-sssd-config
                canary: admin
              defaultShell: "/bin/bash"
              fallbackHomeDir: "/home/%u"
              schema: rfc2307
          ```
        </Accordion>

        <Accordion title="Authentik">
          ```yaml theme={"system"}
          directories:
            - name: coreweave.cloud
              enabled: true
              ldapUri: ldap://authentik-outpost-ldap-outpost
              user:
                bindDn: cn=ldapsvc,dc=coreweave,dc=cloud
                searchBase: dc=coreweave,dc=cloud
                existingSecret: bind-user-sssd-config
                canary: ldapsvc
              startTLS: true
              userObjectClass: user
              groupObjectClass: group
              userNameAttr: cn
              groupNameAttr: cn
              schema: rfc2307bis
          ```
        </Accordion>

        <Accordion title="Active Directory">
          ```yaml theme={"system"}
          directories:
            - name: contoso.com
              enabled: true
              ldapUri: ldap://domaincontroller.tenant-my-tenant.coreweave.cloud
              user:
                bindDn: CN=binduser,CN=Users,DC=contoso,DC=com
                searchBase: DC=contoso,DC=com
                existingSecret: bind-user-sssd-config
                canary: binduser
              defaultShell: "/bin/bash"
              fallbackHomeDir: "/home/%u"
              schema: AD
          ```
        </Accordion>
      </td>

      <td>list</td>
      <td> </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--additionalConfig">
        <b>directoryService.directories\[0].additionalConfig</b><br />
        Multi-line string of additional arbitrary config per domain for sssd. <br />

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          additionalConfig: |
            ldap_foo = bar
          ```
        </Accordion>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--defaultShell">
        <b>directoryService.directories\[0].defaultShell</b><br />
        The default user shell.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/bin/bash"
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--enabled">
        <b>directoryService.directories\[0].enabled</b><br />
        Enable the directory service.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--fallbackHomeDir">
        <b>directoryService.directories\[0].fallbackHomeDir</b><br />
        The fallback user home directory.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/home/%u"
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--ignoreGroupMembers">
        <b>directoryService.directories\[0].ignoreGroupMembers</b><br />
        This overrides SSSD configuration of the same name <br /> If set to <code>true</code>, SSSD only retrieves information about the group objects <br /> themselves and not their members, providing a significant performance boost. <br /> If omitted, defaults to <code>true</code>.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--ldapUri">
        <b>directoryService.directories\[0].ldapUri</b><br />
        The LDAP URI to use for the directory service. <br /> Example: <code>ldap\://YOUR\_LDAP\_IP</code> <br /> For Google Secure LDAP, use: <code>ldaps\://ldap.google.com:636</code> <br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--ldapsCert">
        <b>directoryService.directories\[0].ldapsCert</b><br />
        Name of existing TLS certificate for LDAP-S. <br />

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          kubectl create secret tls google-ldaps-cert \
                  --cert=Google_2025_08_24_55726.crt \
                  --key=Google_2025_08_24_55726.key
          ```
        </Accordion>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--name">
        <b>directoryService.directories\[0].name</b><br />
        Name of the directory service. <br /> The primary domain should always be named: <code>default</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "default"
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--overrideGidAttr">
        <b>directoryService.directories\[0].overrideGidAttr</b><br />
        Override the default schema LDAP attribute that corresponds to the user's primary group id. <br /> Example: <code>posixGid</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--overrideHomeDir">
        <b>directoryService.directories\[0].overrideHomeDir</b><br />
        Override the homeDirectory attribute from LDAP with a provided path. <br /> Example: <code>/mnt/nvme/home/%u</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--overrideUidAttr">
        <b>directoryService.directories\[0].overrideUidAttr</b><br />
        Override the default schema LDAP attribute that corresponds to the user's id. <br /> Example: <code>posixUid</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--overrideUserNameAttr">
        <b>directoryService.directories\[0].overrideUserNameAttr</b><br />
        Override the default schema LDAP attribute that corresponds to the user's login name. <br /> Example: <code>employeeNumber</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--schema">
        <b>directoryService.directories\[0].schema</b><br />
        The desired LDAP schema for the directory service. Valid values: <ul> <li><code>AD</code></li> <li><code>POSIX</code></li> <li><code>rfc2307bis</code></li> </ul> Note: For Google Secure LDAP, use <code>rfc2307bis</code>.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "AD"
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--user--bindDn">
        <b>directoryService.directories\[0].user.bindDn</b><br />
        The LDAP bind DN to use for the directory service. <br /> Where bindDn is not required (e.g. Google Secure LDAP), only supply <code>user.canary</code>. <br /> Example: <code>cn=Admin,ou=Users,ou=CORP,dc=corp,dc=example,dc=com</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--user--canary">
        <b>directoryService.directories\[0].user.canary</b><br />
        The username to lookup to confirm LDAP is working.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--user--existingSecret">
        <b>directoryService.directories\[0].user.existingSecret</b><br />
        Name of an existing secret containing an SSSD configuration snippet with the <code>ldap\_default\_authtok</code> set for this domain.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--user--existingSecretFileName">
        <b>directoryService.directories\[0].user.existingSecretFileName</b><br />
        The name of the file in the existing secret that contains the ldap passwords.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "ldap-password.conf"
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--user--groupSearchBase">
        <b>directoryService.directories\[0].user.groupSearchBase</b><br />
        The LDAP group search base to use for the directory service. <br /> Example: <code>ou=groups,dc=example,dc=com</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--user--password">
        <b>directoryService.directories\[0].user.password</b><br />
        The password to use for the directory service lookups.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--directories[0]--user--searchBase">
        <b>directoryService.directories\[0].user.searchBase</b><br />
        The LDAP search base to use for the directory service. <br /> Example: <code>dc=corp,dc=example,dc=com</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--negativeCacheTimeout">
        <b>directoryService.negativeCacheTimeout</b><br />
        Negative caching value (in seconds). <br /> Determines how long an invalid entry will be cached before asking LDAP again. This improves the directory listing time when a primary gid cannot be found.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "600"
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--sudoGroups">
        <b>directoryService.sudoGroups</b><br />
        List of Unix groups from all directories with sudo privileges. <br /> Group names are fully-qualified for additional directories. Group names <strong>are not</strong> fully-qualified for the default directory; (e.g. "group1" instead of "[group1@domain.com](mailto:group1@domain.com)")
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="directoryService--watchInterval">
        <b>directoryService.watchInterval</b><br />
        The interval in seconds to check for changes in sssd configuration.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        60
        ```
      </td>
    </tr>

    <tr>
      <td id="global--annotations">
        <b>global.annotations</b><br />
        Additional annotations to apply to all resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="global--cks">
        <b>global.cks</b><br />
        Enable CoreWeave Kubernetes Services (CKS) integration.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="global--dnsConfig--additionalSearches">
        <b>global.dnsConfig.additionalSearches</b><br />
        A list of namespaces to add to the list of DNS searches. These additional searches extend hostname lookup in the control-plane, compute, and login pods. Default dns searches: - name-compute.namespace.svc.cluster.local - slurm\_cluster\_name-controller.namespace.svc.cluster.local
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="global--imagePullPolicy">
        <b>global.imagePullPolicy</b><br />
        The image pull policy for all containers.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "IfNotPresent"
        ```
      </td>
    </tr>

    <tr>
      <td id="global--labels">
        <b>global.labels</b><br />
        Additional labels to apply to the all resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="global--nodeSelector--affinity">
        <b>global.nodeSelector.affinity</b><br />
        The affinity for the Slurm control-plane components.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        nodeAffinity:
            requiredDuringSchedulingIgnoredDuringExecution:
                nodeSelectorTerms:
                    - matchExpressions:
                        - key: node.coreweave.cloud/class
                          operator: In
                          values:
                            - cpu

        ```
      </td>
    </tr>

    <tr>
      <td id="global--volumeMounts">
        <b>global.volumeMounts</b><br />
        The list of volume mounts to apply to all compute, controller, accounting, and login pods
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="global--volumes">
        <b>global.volumes</b><br />
        The list of volumes to mount to all compute, controller, accounting, and login pods
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="imagePullSecrets">
        <b>imagePullSecrets</b><br />
        The list of secrets used to access images in a <a href="https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/"> private registry</a>.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="jwt--existingSecret">
        <b>jwt.existingSecret</b><br />
        The name of an existing secret containing the JWT private key, otherwise the chart will generate one.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="login--annotations">
        <b>login.annotations</b><br />
        Additional annotations.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="login--automountServiceAccountToken">
        <b>login.automountServiceAccountToken</b><br />
        Automatically mount the service account token into the login pod.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="login--containers">
        <b>login.containers</b><br />
        Additional sidecar containers to add to the login pod.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="login--enabled">
        <b>login.enabled</b><br />
        Enable the login nodes
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="login--env">
        <b>login.env</b><br />
        Additional environment variables to pass to the sshd container.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="login--hostAliases">
        <b>login.hostAliases</b><br />
        Provides Pod-level override of hostname resolution when DNS and other options are not applicable in login pods. See <a href="https://kubernetes.io/docs/tasks/network/customize-hosts-file-for-pods/"> Adding entries to Pod /etc/hosts with HostAliases</a> for more information.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="login--image">
        <b>login.image</b><br />
        The image to use for the login node.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        name: controller-extras
        repository:
        tag:

        ```
      </td>
    </tr>

    <tr>
      <td id="login--individualResources">
        <b>login.individualResources</b><br />
        Resources for the slurm-login pod sshd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 2Gi
        requests:
            cpu: 500m
            memory: 300Mi

        ```
      </td>
    </tr>

    <tr>
      <td id="login--labels">
        <b>login.labels</b><br />
        Additional labels.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="login--nodeSelector--affinity">
        <b>login.nodeSelector.affinity</b><br />
        The affinity for the login nodes. This overrides the value of <a href="https://docs.coreweave.com/products/sunk/reference/slurm-parameters#global--nodeSelector--affinity"> <code>global.nodeSelector.affinity</code></a>.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="login--priorityClassName">
        <b>login.priorityClassName</b><br />
        The priority class name for the login pod.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="login--replicas">
        <b>login.replicas</b><br />
        The number of replicas of the login node. <br /> When running more than one, a pod specific-service is created for each one in addition to the main service.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        1
        ```
      </td>
    </tr>

    <tr>
      <td id="login--resources--limits--memory">
        <b>login.resources.limits.memory</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "8Gi"
        ```
      </td>
    </tr>

    <tr>
      <td id="login--resources--requests--cpu">
        <b>login.resources.requests.cpu</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        4
        ```
      </td>
    </tr>

    <tr>
      <td id="login--resources--requests--memory">
        <b>login.resources.requests.memory</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "8Gi"
        ```
      </td>
    </tr>

    <tr>
      <td id="login--s6">
        <b>login.s6</b><br />
        <strong>oneshot</strong> and <strong>longrun</strong> jobs are supported. See <a href="https://docs.coreweave.com/products/sunk/run_workloads/run-scripts-with-s6">Running Scripts with S6</a> for more information.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          s6:
            packages:
              type: oneshot
              timeoutUp: 0
              timeoutDown: 0
              script: |
                #!/usr/bin/env bash
                apt -y update
                apt -y install nginx
            nginx:
              type: longrun
              timeoutUp: 0
              timeoutDown: 0
              script: |
                #!/usr/bin/env bash
                nginx -g "daemon off;"
          ```
        </Accordion>
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--additionalPorts">
        <b>login.service.additionalPorts</b><br />
        Additional port definitions to expose.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          additionalPorts:
            - name: eternal-shell
              port: 2022
              targetPort: 20222 # optional
              protocol: TCP # optional
          ```
        </Accordion>
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--enabled">
        <b>login.service.enabled</b><br />
        Enable the creation of service(s) for login pods.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--externalTrafficPolicy">
        <b>login.service.externalTrafficPolicy</b><br />
        The external traffic policy.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "Local"
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--loadBalancerClass">
        <b>login.service.loadBalancerClass</b><br />
        The load balancer class to use for the login services.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--metadata--0--annotations">
        <b>login.service.metadata.0.annotations</b><br />
        Additional annotations to apply to the first login service (0).
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--metadata--0--labels">
        <b>login.service.metadata.0.labels</b><br />
        Additional labels to apply to the common first login service (0).
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--metadata--common--annotations">
        <b>login.service.metadata.common.annotations</b><br />
        Additional annotations to apply to the common login service.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--metadata--common--labels">
        <b>login.service.metadata.common.labels</b><br />
        Additional labels to apply to the common login service.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--metadata--global--annotations">
        <b>login.service.metadata.global.annotations</b><br />
        Additional annotations to apply to all login services.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--metadata--global--labels">
        <b>login.service.metadata.global.labels</b><br />
        Additional labels to apply to all login services.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="login--service--type">
        <b>login.service.type</b><br />
        The type of service to create. This defaults to <code>LoadBalancer</code> for cloud deployments. For development and test systems without an external load balancer to handle the service routing, such as when deploying on <a href="https://kind.sigs.k8s.io/"> kind (Kubernetes IN Docker)</a>, this may be set to <code>ClusterIP</code>.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "LoadBalancer"
        ```
      </td>
    </tr>

    <tr>
      <td id="login--serviceAccountName">
        <b>login.serviceAccountName</b><br />
        The service account name to use for the login pod.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "default"
        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshKeyVolume--accessModes">
        <b>login.sshKeyVolume.accessModes</b><br />
        The access mode for the storage. If scaling login beyond 1 replica, this must be <code>ReadWriteMany</code>. In a development setting with a volume provider that doesn't support <code>ReadWriteMany</code>, such as <a href="https://kind.sigs.k8s.io/"> kind (Kubernetes IN Docker)</a>, this may be set to <code>ReadWriteOnce</code>.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        [
          "ReadWriteMany"
        ]
        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshKeyVolume--enabled">
        <b>login.sshKeyVolume.enabled</b><br />
        Enable the ssh key volume, to allow keys to be mounted and persisted in the login pod.<br /> If this is disabled the host keys for the login pod will be regenerated on each container restart.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshKeyVolume--size">
        <b>login.sshKeyVolume.size</b><br />
        The size of the persistent volume claim.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "1Gi"
        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshKeyVolume--storageClassName">
        <b>login.sshKeyVolume.storageClassName</b><br />
        The storage class name to use for the volume.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "shared-vast"
        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshdConfig">
        <b>login.sshdConfig</b><br />
        Additional sshd configuration to add to the login pod.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          sshdConfig:
            PasswordAuthentication: "no"
          ```
        </Accordion>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshdLivenessProbe--config">
        <b>login.sshdLivenessProbe.config</b><br />
        The liveness probe for the login sshd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        failureThreshold: 10
        initialDelaySeconds: 10
        periodSeconds: 5
        tcpSocket:
            port: 22

        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshdLivenessProbe--enabled">
        <b>login.sshdLivenessProbe.enabled</b><br />
        If the liveness probe for the login sshd is enabled
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshdReadinessProbe--config">
        <b>login.sshdReadinessProbe.config</b><br />
        The readiness probe for the login sshd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshdReadinessProbe--enabled">
        <b>login.sshdReadinessProbe.enabled</b><br />
        If the readiness probe for the login sshd container is enabled
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshdStartupProbe--config">
        <b>login.sshdStartupProbe.config</b><br />
        The startup probe for the login sshd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="login--sshdStartupProbe--enabled">
        <b>login.sshdStartupProbe.enabled</b><br />
        If the startup probe for the login sshd container is enabled
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="login--terminationGracePeriodSeconds">
        <b>login.terminationGracePeriodSeconds</b><br />
        The termination grace period for the login pod.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        30
        ```
      </td>
    </tr>

    <tr>
      <td id="login--updateStrategy">
        <b>login.updateStrategy</b><br />
        The update strategy for the login node- Default is type is RollingUpdate
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="login--volumeMounts">
        <b>login.volumeMounts</b><br />
        Additional volume mounts to apply to the login pod.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="login--volumes">
        <b>login.volumes</b><br />
        Additional volumes to add to the login pod.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          volumes:
            - name: cache-vol
              emptyDir:
                medium: Memory
          ```
        </Accordion>
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="moco">
        <b>moco</b><br />
        Options for MOCO MySQL used for Slurm job accounting.
      </td>

      <td>object</td>
      <td>See individual settings below.</td>
    </tr>

    <tr>
      <td id="moco--enabled">
        <b>moco.enabled</b><br />
        Enable moco.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="moco--migration--enabled">
        <b>moco.migration.enabled</b><br />
        When enabled: true, a Kubernetes Job is created to perform the migration of the Slurm accounting database to MOCO MySQL. This job runs once and then completes. Any existing Slurm accounting database in bitnami MySQL database will be migrated to the MOCO MySQL database. This should be set to true only for the initial migration, and then set to false afterwards to bring the cluster back to normal operation. During this automated migration, the Slurm cluster will not be in a functional state.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--affinity">
        <b>moco.mysqlCluster.affinity</b><br />
        Optional pod affinity configuration
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--auth--existingSecret">
        <b>moco.mysqlCluster.auth.existingSecret</b><br />
        Optional, will use randomly generated moco `WRITABLE_PASSWORD` if not set Specify the name of the Kubernetes Secret that contains the password used by <code>slurmdbd</code> to access the MOCO MySQL database. This Secret <strong>must</strong> contain a data key named <code>WRITABLE\_PASSWORD</code> whose value is the actual database password.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--auth--storageHost">
        <b>moco.mysqlCluster.auth.storageHost</b><br />
        The hostname of the server where the database resides.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "moco-{{ .Release.Name }}"
        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--auth--storageLoc">
        <b>moco.mysqlCluster.auth.storageLoc</b><br />
        The name of the database used to store Slurm accounting records. Defaults to "slurm\_acct\_db".
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "slurm_acct_db"
        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--auth--storageUser">
        <b>moco.mysqlCluster.auth.storageUser</b><br />
        The username <code>slurmdbd</code> uses for authentication and storing job accounting data.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "moco-writable"
        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--config">
        <b>moco.mysqlCluster.config</b><br />
        Additional MySQL configuration to add to the mysqlCluster. This will be placed in a ConfigMap and referenced by the mysqlCluster. The contents of the configmap will be rendered as a template, so helm expressions can be used. This needs to render as valid yaml. <a href="https://dev.mysql.com/doc/refman/en/option-files.html">MySQL option file documentation</a>

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          config: |
            max_connections: 1000
            wait_timeout: 28800
          ```
        </Accordion>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--image">
        <b>moco.mysqlCluster.image</b><br />
        The image to use for mysql.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        repository: ghcr.io/cybozu-go/moco/mysql
        tag: 8.4.6

        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--inodeLockFixer--enabled">
        <b>moco.mysqlCluster.inodeLockFixer.enabled</b><br />
        Configure init container to fix inode locking issues. This init container copies, moves, and replaces the MySQL data directory to prevent known inode locking issues that can occur in certain storage environments.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--inodeLockFixer--image">
        <b>moco.mysqlCluster.inodeLockFixer.image</b><br />
        The image to use for the inode lock fixer init container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        repository: alpine
        tag: 3.20.0

        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--persistence">
        <b>moco.mysqlCluster.persistence</b><br />
        The volume settings to use for mysql.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        storageClassName:
        size: 128Gi
        accessModes:
            - ReadWriteOnce

        ```
      </td>
    </tr>

    <tr>
      <td id="moco--mysqlCluster--resources">
        <b>moco.mysqlCluster.resources</b><br />
        Resources for the moco mysqld container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        requests:
            memory: 64Gi
            cpu: "16"
        limits:
            memory: 64Gi

        ```
      </td>
    </tr>

    <tr>
      <td id="moco--priorityClassName">
        <b>moco.priorityClassName</b><br />
        The priority class name for moco.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sunk-control-plane"
        ```
      </td>
    </tr>

    <tr>
      <td id="munge--args">
        <b>munge.args</b><br />
        The additional arguments to pass to the munge container. The defaults run Munge with 10 threads instead of 2.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        [
          "--num-threads",
          "10"
        ]
        ```
      </td>
    </tr>

    <tr>
      <td id="munge--livenessProbe">
        <b>munge.livenessProbe</b><br />
        Liveness probe for the munge container.  When munged hangs (e.g. thread deadlock), `munge -n` blocks on the Unix socket and the probe times out, causing Kubernetes to restart only the munged container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        exec:
            command: ["munge", "-n"]
        initialDelaySeconds: 60
        periodSeconds: 180
        timeoutSeconds: 180
        failureThreshold: 5

        ```
      </td>
    </tr>

    <tr>
      <td id="munge--readinessProbe">
        <b>munge.readinessProbe</b><br />
        The readiness probe for the munge container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="munge--resources">
        <b>munge.resources</b><br />
        Resources for the munge container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 2Gi
        requests:
            cpu: 1
            memory: 2Gi

        ```
      </td>
    </tr>

    <tr>
      <td id="munge--securityContext--runAsGroup">
        <b>munge.securityContext.runAsGroup</b><br />
        The group to run as, must match the munge GID from the container image.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        400
        ```
      </td>
    </tr>

    <tr>
      <td id="munge--securityContext--runAsUser">
        <b>munge.securityContext.runAsUser</b><br />
        The user to run as, must match the munge UID from the container image.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        400
        ```
      </td>
    </tr>

    <tr>
      <td id="munge--startupProbe">
        <b>munge.startupProbe</b><br />
        The startup probe for the munge container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="mysql">
        <b>mysql</b><br />
        Options for <a href="https://github.com/bitnami/charts/tree/main/bitnami/mysql">Bitnami MySQL chart</a>, uses <a href="https://github.com/bitnami/charts/tree/main/bitnami/mysql">Bitnami default values</a>. There is an added option here: <code>vmPodScrape.enabled</code> which can be used as an alternative to <code>serviceMonitor.enabled</code>.
      </td>

      <td>object</td>
      <td>See Bitnami default values.</td>
    </tr>

    <tr>
      <td id="nsscache--annotations">
        <b>nsscache.annotations</b><br />
        Additional annotations for nsscache Job resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--cronJobSchedule">
        <b>nsscache.cronJobSchedule</b><br />
        The schedule for the nsscache update CronJob. It should be formatted according to the cron convention.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "* * * * *"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--enabled">
        <b>nsscache.enabled</b><br />
        Enable nsscache.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--existingSecret">
        <b>nsscache.existingSecret</b><br />
        Name of an existing secret containing the LDAP password for this domain. This secret should contain a key named <code>nsscache-ldap-password</code> which contains the password to use for the LDAP bind DN. For SCIM, this secret should contain a key named <code>nsscache-scim-auth-token</code> which contains the token to use for the SCIM server.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--labels">
        <b>nsscache.labels</b><br />
        Additional labels for nsscache Job resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nodeSelector--affinity">
        <b>nsscache.nodeSelector.affinity</b><br />
        The affinity for the nsscache Job. This overrides the value of <a href="https://docs.coreweave.com/products/sunk/reference/slurm-parameters#global--nodeSelector--affinity"> <code>global.nodeSelector.affinity</code></a>.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig">
        <b>nsscache.nsscacheConfig</b><br />
        Options for defining nsscache.conf. Click to exapand examples.

        <Accordion title="LDAP">
          ```yaml theme={"system"}
          nsscacheConfig:
            default:
              source: ldap
              ldap_uri: ldap://authentik-outpost-ldap-outpost
              ldap_base: dc=coreweave,dc=cloud
              ldap_bind_dn: cn=ldapsvc,dc=coreweave,dc=cloud
              ldap_bind_password:
              ldap_rfc2307bis: 1
              ldap_default_shell: /bin/bash
              ldap_scope: sub
              ldap_uidattr: cn
            passwd:
              ldap_filter: (objectClass=user)
              ldap_override_home_dir: /mnt/home/%%u
            group:
              ldap_filter: (objectClass=group)
            shadow:
              ldap_filter: (objectClass=user)
            sshkey:
              ldap_filter: (objectClass=user)
          ```
        </Accordion>

        <Accordion title="SCIM">
          ```yaml theme={"system"}
          nsscacheConfig:
            default:
              source: scim
              scim_base_url: https://api.coreweave.com/scim/abc123
              scim_users_parameters: filter=active eq "true"&groups=slurm-users,slurm-admins
              scim_groups_parameters: excludeInactiveUsers=true&includeVirtualUserGroups=slurm-users,slurm-admins
          ```
        </Accordion>
      </td>

      <td>object</td>
      <td>See the <a href="https://manpages.ubuntu.com/manpages/jammy/man5/nsscache.conf.5.html">nsscache.conf documentation</a>.</td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--cache">
        <b>nsscache.nsscacheConfig.default.cache</b><br />
        Specifying the means in which the cache data will be stored.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "files"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--files_cache_filename_suffix">
        <b>nsscache.nsscacheConfig.default.files\_cache\_filename\_suffix</b><br />
        A suffix appended to the cache filename to differentiate it from, say, system NSS databases.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "cache"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--files_dir">
        <b>nsscache.nsscacheConfig.default.files\_dir</b><br />
        Directory location to store the plain text files in.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/etc/nsscache"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--ldap_base">
        <b>nsscache.nsscacheConfig.default.ldap\_base</b><br />
        The base to perform LDAP searches under. <br /> Example: <code>dc=coreweave,dc=cloud</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--ldap_bind_dn">
        <b>nsscache.nsscacheConfig.default.ldap\_bind\_dn</b><br />
        The bind DN to use when connecting to LDAP. Empty string is an anonymous bind. <br /> Example: <code>cn=ldapsvc,dc=coreweave,dc=cloud</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--ldap_bind_password">
        <b>nsscache.nsscacheConfig.default.ldap\_bind\_password</b><br />
        The password to use for the LDAP bind DN. We strongly recommend using a Kubernetes secret to store this password and reference it using the <code>nsscache.existingSecret</code> value.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--ldap_default_shell">
        <b>nsscache.nsscacheConfig.default.ldap\_default\_shell</b><br />
        This will be the default shell for all users. You can specify a different shell by setting the <code>loginShell</code> value in the user attributes in the source directory configuration. <br /> Example: <code>/bin/bash</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--ldap_rfc2307bis">
        <b>nsscache.nsscacheConfig.default.ldap\_rfc2307bis</b><br />
        Example: <code>1</code>
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--ldap_scope">
        <b>nsscache.nsscacheConfig.default.ldap\_scope</b><br />
        The search scope to use for LDAP. Example: <code>sub</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--ldap_uidattr">
        <b>nsscache.nsscacheConfig.default.ldap\_uidattr</b><br />
        The uid-like attribute in your LDAP directory. Example: <code>cn</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--ldap_uri">
        <b>nsscache.nsscacheConfig.default.ldap\_uri</b><br />
        The LDAP URI to connect to. <br /> Example: <code>ldap\://authentik-outpost-ldap-outpost</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--maps">
        <b>nsscache.nsscacheConfig.default.maps</b><br />
        The recommended defaults below are useful for standard nsscache operation in many environments.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        [
          "passwd",
          "shadow",
          "group",
          "sshkey"
        ]
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--scim_base_url">
        <b>nsscache.nsscacheConfig.default.scim\_base\_url</b><br />
        The base URL for the SCIM server. <br /> Example: `https://api.coreweave.com/scim/<org>`
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--scim_groups_endpoint">
        <b>nsscache.nsscacheConfig.default.scim\_groups\_endpoint</b><br />
        The endpoint for the SCIM groups API.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "CoreWeaveGroups"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--scim_groups_parameters">
        <b>nsscache.nsscacheConfig.default.scim\_groups\_parameters</b><br />
        Option to use url parameters for groups endpoint. Special characters (spaces, quotes, etc.) will be automatically URL encoded. There is a custom parameter for creating virtual user groups that is a comma separated list. It will create an entry in the groups map for the user's gid for the members of the selected group(s). This parameter typically should match any group filtering in scim\_users\_parameters. Including a filter for inactive users by default. <br /> Example: <code>excludeInactiveUsers=true\&includeVirtualUserGroups=slurm-users,slurm-admins </code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "excludeInactiveUsers=true"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--scim_users_endpoint">
        <b>nsscache.nsscacheConfig.default.scim\_users\_endpoint</b><br />
        The endpoint for the SCIM users API.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "Users"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--scim_users_parameters">
        <b>nsscache.nsscacheConfig.default.scim\_users\_parameters</b><br />
        Option to use url parameters for users endpoint. Special characters (spaces, quotes, etc.) will be automatically URL encoded. There is a custom parameter for filtering by groups that is a comma separated list. Including a filter for inactive users by default. <br /> Example: <code>filter=active eq "true"\&groups=slurm-users,slurm-admins</code>
      </td>

      <td>string</td>
      <td><code>filter=active eq "true"</code></td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--source">
        <b>nsscache.nsscacheConfig.default.source</b><br />
        Specify the data source to use. Supported options are `scim` and `ldap`.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "scim"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--default--timestamp_dir">
        <b>nsscache.nsscacheConfig.default.timestamp\_dir</b><br />
        Specifying the location of the timestamps used for incremental updates.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/var/lib/nsscache"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--group--scim_path_gid">
        <b>nsscache.nsscacheConfig.group.scim\_path\_gid</b><br />
        The SCIM path for the GID attribute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sunkPosixGroupId"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--group--scim_path_groupname">
        <b>nsscache.nsscacheConfig.group.scim\_path\_groupname</b><br />
        The SCIM path for the group name attribute. Used when the SCIM server provides a custom field for group names. If not specified or the path returns no value, nsscache will fall back to using displayName, name, or id from the SCIM group resource.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sunkPosixGroupName"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--group--scim_path_username">
        <b>nsscache.nsscacheConfig.group.scim\_path\_username</b><br />
        The SCIM path for the GID attribute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "members/sunkPosixUsername"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--passwd--ldap_filter">
        <b>nsscache.nsscacheConfig.passwd.ldap\_filter</b><br />
        The search filter to use when querying. <br /> Example: <code>(objectClass=user)</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--passwd--ldap_override_home_dir">
        <b>nsscache.nsscacheConfig.passwd.ldap\_override\_home\_dir</b><br />
        This will override the home directory all users. %%u will be replaced with the username. this should match the mount found in compute.VolumeMounts <br /> Example: <code>/mtn/home/%%u</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--passwd--scim_default_shell">
        <b>nsscache.nsscacheConfig.passwd.scim\_default\_shell</b><br />
        This will be the default shell for all users.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/bin/bash"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--passwd--scim_override_home_directory">
        <b>nsscache.nsscacheConfig.passwd.scim\_override\_home\_directory</b><br />
        This will override the home directory all users. %%u will be replaced with the username. this should match the mount found in compute.VolumeMounts <br /> Example: <code>/mnt/home/%%u</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/mnt/home/%%u"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--passwd--scim_path_gid">
        <b>nsscache.nsscacheConfig.passwd.scim\_path\_gid</b><br />
        The SCIM path for the GID attribute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "urn:coreweave:params:scim:schemas:extension:coreweave:2.0:CoreWeaveUser/sunkPosixGroupId"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--passwd--scim_path_home_directory">
        <b>nsscache.nsscacheConfig.passwd.scim\_path\_home\_directory</b><br />
        The SCIM path for the home directory attribute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "urn:coreweave:params:scim:schemas:extension:coreweave:2.0:CoreWeaveUser/sunkPreferredHomeDirectory"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--passwd--scim_path_login_shell">
        <b>nsscache.nsscacheConfig.passwd.scim\_path\_login\_shell</b><br />
        The SCIM path for the login shell attribute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "urn:coreweave:params:scim:schemas:extension:coreweave:2.0:CoreWeaveUser/sunkLoginShell"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--passwd--scim_path_uid">
        <b>nsscache.nsscacheConfig.passwd.scim\_path\_uid</b><br />
        The SCIM path for the UID attribute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "urn:coreweave:params:scim:schemas:extension:coreweave:2.0:CoreWeaveUser/sunkPosixUserId"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--passwd--scim_path_username">
        <b>nsscache.nsscacheConfig.passwd.scim\_path\_username</b><br />
        The SCIM path for the username attribute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "urn:coreweave:params:scim:schemas:extension:coreweave:2.0:CoreWeaveUser/sunkPosixUsername"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--shadow--ldap_filter">
        <b>nsscache.nsscacheConfig.shadow\.ldap\_filter</b><br />
        The search filter to use when querying. <br /> Example: <code>(objectClass=user)</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--shadow--scim_path_username">
        <b>nsscache.nsscacheConfig.shadow\.scim\_path\_username</b><br />
        The SCIM path for the username attribute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "urn:coreweave:params:scim:schemas:extension:coreweave:2.0:CoreWeaveUser/sunkPosixUsername"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--sshkey--ldap_filter">
        <b>nsscache.nsscacheConfig.sshkey.ldap\_filter</b><br />
        The search filter to use when querying. <br /> Example: <code>(objectClass=user)</code>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--sshkey--scim_path_ssh_keys">
        <b>nsscache.nsscacheConfig.sshkey.scim\_path\_ssh\_keys</b><br />
        The SCIM path for the SSH keys attribute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "urn:coreweave:params:scim:schemas:extension:coreweave:2.0:CoreWeaveUser/sunkSshKeys"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsscacheConfig--sshkey--scim_path_username">
        <b>nsscache.nsscacheConfig.sshkey.scim\_path\_username</b><br />
        The SCIM path for the username attribute.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "urn:coreweave:params:scim:schemas:extension:coreweave:2.0:CoreWeaveUser/sunkPosixUsername"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig">
        <b>nsscache.nsswitchConfig</b><br />
        Options for defining nsswitch.conf.
      </td>

      <td>object</td>
      <td>See the <a href="https://manpages.ubuntu.com/manpages/jammy/man5/nsswitch.conf.5.html">nsswitch.conf documentation</a>.</td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--aliases">
        <b>nsscache.nsswitchConfig.aliases</b><br />
        Mail aliases, used by getaliasent(3) and related functions.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--ethers">
        <b>nsscache.nsswitchConfig.ethers</b><br />
        Ethernet numbers.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--group">
        <b>nsscache.nsswitchConfig.group</b><br />
        Groups of users, used by getgrent(3) and related functions.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        [
          "files",
          "cache"
        ]
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--hosts">
        <b>nsscache.nsswitchConfig.hosts</b><br />
        Host names and numbers, used by gethostbyname(3) and related functions.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--initgroups">
        <b>nsscache.nsswitchConfig.initgroups</b><br />
        Supplementary group access list, used by getgrouplist(3) function.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--netgroup">
        <b>nsscache.nsswitchConfig.netgroup</b><br />
        Network-wide list of hosts and users, used for access rules. C libraries before glibc 2.1 supported netgroups only over NIS.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--networks">
        <b>nsscache.nsswitchConfig.networks</b><br />
        Network names and numbers, used by getnetent(3) and related functions.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--passwd">
        <b>nsscache.nsswitchConfig.passwd</b><br />
        User passwords, used by getpwent(3) and related functions.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        [
          "files",
          "cache"
        ]
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--protocols">
        <b>nsscache.nsswitchConfig.protocols</b><br />
        Network protocols, used by getprotoent(3) and related functions.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--publickey">
        <b>nsscache.nsswitchConfig.publickey</b><br />
        Public and secret keys for Secure\_RPC used by NFS and NIS+.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--rpc">
        <b>nsscache.nsswitchConfig.rpc</b><br />
        Remote procedure call names and numbers, used by getrpcbyname(3) and related functions.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--services">
        <b>nsscache.nsswitchConfig.services</b><br />
        Network services, used by getservent(3) and related functions.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--nsswitchConfig--shadow">
        <b>nsscache.nsswitchConfig.shadow</b><br />
        Shadow user passwords, used by getspnam(3) and related functions.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--priorityClassName">
        <b>nsscache.priorityClassName</b><br />
        The priority class name for the nsscache Job pod.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sunk-control-plane"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--resources">
        <b>nsscache.resources</b><br />
        Resources for the nsscache Job container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 500Mi
        requests:
            cpu: 200m
            memory: 100Mi

        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--slurmUserProvisioning--defaultSlurmAccount">
        <b>nsscache.slurmUserProvisioning.defaultSlurmAccount</b><br />
        The default Slurm account for automated provisioning of users.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "cw-sup"
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--slurmUserProvisioning--dryRun">
        <b>nsscache.slurmUserProvisioning.dryRun</b><br />
        Enable dry run mode - shows what would be done without making changes.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--slurmUserProvisioning--enabled">
        <b>nsscache.slurmUserProvisioning.enabled</b><br />
        Enable slurmUserProvisioning.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--slurmUserProvisioning--interval">
        <b>nsscache.slurmUserProvisioning.interval</b><br />
        The interval in seconds between user sync runs.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        60
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--sudoGroups">
        <b>nsscache.sudoGroups</b><br />
        List of Unix groups with sudo privileges.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="nsscache--tolerations">
        <b>nsscache.tolerations</b><br />
        The tolerations for the nsscache Job
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--annotations">
        <b>rest.annotations</b><br />
        Additional annotations for REST API resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--args">
        <b>rest.args</b><br />
        The additional arguments to pass to the rest container. Defaults enable debug logging and only load most recent openAPI plugins.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        [
          "-vv",
          "-sslurmdbd,slurmctld",
          "-dv0.0.40"
        ]
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--containers">
        <b>rest.containers</b><br />
        Additional sidecar containers to add to the restd pod.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--enabled">
        <b>rest.enabled</b><br />
        Enable the REST API deployment <br /> This is optional and should be disabled for most use cases.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--env">
        <b>rest.env</b><br />
        The additional environment variables to pass to the rest container.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        [
          {
            "name": "SLURMRESTD_JSON",
            "value": "compact"
          }
        ]
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--image">
        <b>rest.image</b><br />
        The image to use for the REST API deployment.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        name: controller
        repository:
        tag:

        ```
      </td>
    </tr>

    <tr>
      <td id="rest--labels">
        <b>rest.labels</b><br />
        Additional labels for REST API resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--livenessProbe">
        <b>rest.livenessProbe</b><br />
        The liveness probe for the rest container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        tcpSocket:
            port: slurmrestd
        failureThreshold: 2
        periodSeconds: 10

        ```
      </td>
    </tr>

    <tr>
      <td id="rest--priorityClassName">
        <b>rest.priorityClassName</b><br />
        The priority class name for the rest pod.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--readinessProbe">
        <b>rest.readinessProbe</b><br />
        The readiness probe for the rest container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        tcpSocket:
            port: slurmrestd
        periodSeconds: 5
        failureThreshold: 1

        ```
      </td>
    </tr>

    <tr>
      <td id="rest--replicas">
        <b>rest.replicas</b><br />
        The number of replicas of the rest pod to run. <br /> In most production environments this should be set to a minimum of 2 to provide HA.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        1
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--resources">
        <b>rest.resources</b><br />
        Resources for the slurmrestd container. <br /> These defaults are appropriate for small and medium-sized clusters.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 64Gi
        requests:
            cpu: 2
            memory: 8Gi

        ```
      </td>
    </tr>

    <tr>
      <td id="rest--securityContext--runAsGroup">
        <b>rest.securityContext.runAsGroup</b><br />
        The group to run as, GID must exist in the container image.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        65534
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--securityContext--runAsUser">
        <b>rest.securityContext.runAsUser</b><br />
        The user to run as, UID must exist in the container image.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        65534
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--service--additionalPorts">
        <b>rest.service.additionalPorts</b><br />
        Additional port definitions to expose.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          additionalPorts:
            - name: proxy
              port: 8080
              targetPort: 8080 # optional
              protocol: TCP # optional
          ```
        </Accordion>
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--service--annotations">
        <b>rest.service.annotations</b><br />
        Additional annotations to apply to rest service.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--service--clusterIP">
        <b>rest.service.clusterIP</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "None"
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--service--enabled">
        <b>rest.service.enabled</b><br />
        Enable the creation of service for rest pods.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--service--externalTrafficPolicy">
        <b>rest.service.externalTrafficPolicy</b><br />
        The external traffic policy.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--service--labels">
        <b>rest.service.labels</b><br />
        Additional labels to apply rest service.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--service--loadBalancerClass">
        <b>rest.service.loadBalancerClass</b><br />
        The load balancer class to use for the rest services.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--service--type">
        <b>rest.service.type</b><br />
        The type of service to create. This defaults to <code>ClusterIP</code>.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "ClusterIP"
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--startupProbe">
        <b>rest.startupProbe</b><br />
        The startup probe for the rest container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        tcpSocket:
            port: slurmrestd
        failureThreshold: 20
        periodSeconds: 2

        ```
      </td>
    </tr>

    <tr>
      <td id="rest--terminationGracePeriodSeconds">
        <b>rest.terminationGracePeriodSeconds</b><br />
        The termination grace period for the rest pod.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        5
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--volumeMounts">
        <b>rest.volumeMounts</b><br />
        Additional volume mounts to apply to the rest pod.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="rest--volumes">
        <b>rest.volumes</b><br />
        Additional volumes to add to the restd pod.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          volumes:
            - name: cache-vol
              emptyDir:
                medium: Memory
          ```
        </Accordion>
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--annotations">
        <b>scheduler.annotations</b><br />
        Additional annotations for scheduler resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--config--scheduler--gpuTypes">
        <b>scheduler.config.scheduler.gpuTypes</b><br />
        Mapping of k8s gpu types to Slurm gpu types. The keys represent GPU types required during scheduling from the node affinity using the key "gpu.nvidia.com/class" and the values represent the gres gpu type in Slurm. This gets added to a job's description.
      </td>

      <td>map</td>

      <td>
        ```yaml wrap theme={"system"}
        {
          "A100_NVLINK_80GB": "a100",
          "H100_NVLINK_80GB": "h100"
        }
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--config--scheduler--pollInterval">
        <b>scheduler.config.scheduler.pollInterval</b><br />
        The polling interval for the Slurm API.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "10s"
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--config--scheduler--terminationOffset">
        <b>scheduler.config.scheduler.terminationOffset</b><br />
        offset termination grace period to account for communication delays etc.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "5s"
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--config--slurm--poolSize">
        <b>scheduler.config.slurm.poolSize</b><br />
        The number of connections to be maintained in the connection pool.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        10
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--config--slurm--protocolVersion">
        <b>scheduler.config.slurm.protocolVersion</b><br />
        The protocol version to use for communication with the Slurm controller.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "25_05"
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--config--slurm--usePersistentConnection">
        <b>scheduler.config.slurm.usePersistentConnection</b><br />
        Use Slurm's persistent connections for connection reuse.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--controllerAddress">
        <b>scheduler.controllerAddress</b><br />
        The address of the Slurm controller to connect to. <br /> This should be the service address of the controller in host:port format.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        ""
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--enabled">
        <b>scheduler.enabled</b><br />
        Enable the scheduler. <br /> To schedule k8s pods on the Slurm cluster nodes, this must be enabled.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--hooksAPI">
        <b>scheduler.hooksAPI</b><br />
        config for the webhooks.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {
          "waitForPodDeletionInterval": "1s"
        }
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--hooksAPI--waitForPodDeletionInterval">
        <b>scheduler.hooksAPI.waitForPodDeletionInterval</b><br />
        The polling interval when checking for pod deletion.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "1s"
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--image">
        <b>scheduler.image</b><br />
        The image to use for the scheduler.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        repository: registry.gitlab.com/coreweave/sunk/operator
        tag:

        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--labels">
        <b>scheduler.labels</b><br />
        Additional labels for scheduler resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--livenessProbe">
        <b>scheduler.livenessProbe</b><br />
        The liveness probe for the scheduler container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        httpGet:
            path: /healthz
            port: 8081
        initialDelaySeconds: 15
        periodSeconds: 20

        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--logLevel">
        <b>scheduler.logLevel</b><br />
        The log level. <br /> Uses integers or <a href="https://pkg.go.dev/go.uber.org/zap#pkg-constants">zap log level strings</a>: <ul> <li><code>debug</code></li> <li><code>info</code></li> <li><code>warn</code></li> <li><code>error</code></li> <li><code>dpanic</code></li> <li><code>panic</code></li> <li><code>fatal</code></li> </ul>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "info"
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--maxConcurrentReconciles">
        <b>scheduler.maxConcurrentReconciles</b><br />
        The maximum concurrent reconciles. <br /> This should be adjusted based on the volume of pods using the scheduler to handle bursts operations quickly.  The size of both the Slurm and Kubernetes clusters will impact this but less than the syncer.  The driving factor here tends to be the pod volume and associated Slurm jobs more than anything else.  Using the same value as the syncer should be a rather conservative starting point in many use cases.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        50
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--name">
        <b>scheduler.name</b><br />
        The name of the scheduler used to select the scheduler during pod creation. <br /> By default the name is based on the namespace and release name `<namespace>-<release>-scheduler` when not set.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--priorityClassName">
        <b>scheduler.priorityClassName</b><br />
        The priority class name for the scheduler pod.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sunk-control-plane"
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--readinessProbe">
        <b>scheduler.readinessProbe</b><br />
        The readiness probe for the scheduler container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        httpGet:
            path: /readyz
            port: 8081
        initialDelaySeconds: 5
        periodSeconds: 10

        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--resources">
        <b>scheduler.resources</b><br />
        Resources for the scheduler container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 24Gi
            cpu: 16
        requests:
            cpu: 4
            memory: 24Gi

        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--scope--namespaces">
        <b>scheduler.scope.namespaces</b><br />
        The list of the namespaces to scope the scheduler to. <br /> Only used when <code>scope.type</code> is set to <code>namespace</code>. Namespaces other than the release namespace will need role bindings created.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        [.Release.Namespace]
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--scope--type">
        <b>scheduler.scope.type</b><br />
        The type can be <code>cluster</code> or <code>namespace</code>.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "namespace"
        ```
      </td>
    </tr>

    <tr>
      <td id="scheduler--startupProbe">
        <b>scheduler.startupProbe</b><br />
        The startup probe for the scheduler container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="secretJob--annotations">
        <b>secretJob.annotations</b><br />
        Additional annotations for secret Job resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="secretJob--labels">
        <b>secretJob.labels</b><br />
        Additional labels for secret Job resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="secretJob--nodeSelector--affinity">
        <b>secretJob.nodeSelector.affinity</b><br />
        The affinity for the secret job. This overrides the value of <a href="https://docs.coreweave.com/products/sunk/reference/slurm-parameters#global--nodeSelector--affinity"> <code>global.nodeSelector.affinity</code></a>.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="secretJob--priorityClassName">
        <b>secretJob.priorityClassName</b><br />
        The priority class name for the secret job pod.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sunk-control-plane"
        ```
      </td>
    </tr>

    <tr>
      <td id="secretJob--resources">
        <b>secretJob.resources</b><br />
        Resources for the secret job container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 500Mi
        requests:
            cpu: 200m
            memory: 100Mi

        ```
      </td>
    </tr>

    <tr>
      <td id="secretJob--tolerations">
        <b>secretJob.tolerations</b><br />
        The tolerations for the secret job
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="slurm-login">
        <b>slurm-login</b><br />
        Configure individual login nodes via <code>slurm-login</code> subchart. Below is an example showing some of the key parameters of the subchart, <a href="https://docs.coreweave.com/products/sunk/reference/slurm-login-parameters"> see subchart docs</a> for all parameters.

        <Accordion title="Example: click to expand">
          ```yaml theme={"system"}
          slurm-login:
            enable: true
            directoryCache:
              # select users from two groups
              selectGroups: ["slum-researches", "slurm-ops"]
              # poll every minutes (default 90s)
              interval: 1m
              # enable nsscache source
              source: nsscache

              SSSD options: directoryService is not needed when using nsscache, use only with SSSD.
              # Google Secure LDAP
              directoryService:
                directories:
                  - name: google-example.com
                    enabled: true
                    ldapUri: ldaps://ldap.google.com:636
                    user:
                      canary: user@google-example.com
                    defaultShell: "/bin/bash"
                    fallbackHomeDir: "/home/%u"
                    overrideHomeDir: /mnt/nvme/home/%u
                    ldapsCert: google-ldaps-cert
                    schema: rfc2307bis
          ```
        </Accordion>
      </td>

      <td>object</td>
      <td>See default values in `slurm-login` subchart.</td>
    </tr>

    <tr>
      <td id="slurmConfig--AccountingStorageEnforce">
        <b>slurmConfig.AccountingStorageEnforce</b><br />
        Controls what level of association-based enforcement to impose on job submissions. <br /> Multiple values allowed. Valid options are any combination of: <ul> <li><code>associations</code></li> <li><code>limits</code></li> <li><code>nojobs</code></li> <li><code>nosteps</code></li> <li><code>qos</code></li> <li><code>safe</code></li> <li><code>wckeys</code></li> </ul> Use <code>all</code> to impose everything except <code>nojobs</code> and <code>nosteps</code>, which must be requested separately. See <a href="https://slurm.schedmd.com/slurm.conf.html#OPT_AccountingStorageEnforce">the Slurm documentation</a> for more details.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        [
          "qos",
          "limits"
        ]
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--AccountingStorageTRES">
        <b>slurmConfig.AccountingStorageTRES</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "gres/gpu"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--AccountingStorageType">
        <b>slurmConfig.AccountingStorageType</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "accounting_storage/slurmdbd"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--AuthAltParameters[0]">
        <b>slurmConfig.AuthAltParameters\[0]</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "jwt_key=/etc/jwt/jwt.key"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--AuthAltTypes[0]">
        <b>slurmConfig.AuthAltTypes\[0]</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "auth/jwt"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--BatchStartTimeout">
        <b>slurmConfig.BatchStartTimeout</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        120
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--CommunicationParameters">
        <b>slurmConfig.CommunicationParameters</b><br />
        The list of communication parameters to pass to slurmCtld. See <a href="https://slurm.schedmd.com/slurmctld.html">the Slurm documentation</a> for possible values.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        - KeepAliveTime=60
        - keepaliveinterval=10
        - keepaliveprobes=3

        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--DebugFlags">
        <b>slurmConfig.DebugFlags</b><br />
        Comma-separated debug flags for logging.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "NO_CONF_HASH"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--DefMemPerCPU">
        <b>slurmConfig.DefMemPerCPU</b><br />
        The default memory per CPU in megabytes. <br /> Sets the <a href="https://slurm.schedmd.com/slurm.conf.html#OPT_DefMemPerCPU"> slurm.conf parameter</a> of the default real memory size available per usable allocated CPU in megabytes. This value is used when the <code>--mem-per-cpu</code> option is not specified on the <code>srun</code> command line.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        4096
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--Epilog">
        <b>slurmConfig.Epilog</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/usr/share/sunk/bin/epilog.sh"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--GresTypes[0]">
        <b>slurmConfig.GresTypes\[0]</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "gpu"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--InactiveLimit">
        <b>slurmConfig.InactiveLimit</b><br />
        Terminate job allocation commands, such as <code>srun</code> or <code>salloc</code>, that are unresponsive longer than this interval in seconds. See the <a href="https://slurm.schedmd.com/slurm.conf.html#OPT_InactiveLimit">slurm.conf</a> reference for more details.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        0
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--JobAcctGatherFrequency">
        <b>slurmConfig.JobAcctGatherFrequency</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        30
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--JobAcctGatherType">
        <b>slurmConfig.JobAcctGatherType</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "jobacct_gather/cgroup"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--JobCompType">
        <b>slurmConfig.JobCompType</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "jobcomp/none"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--JobSubmitPlugins">
        <b>slurmConfig.JobSubmitPlugins</b><br />
        The job submit plugins to use. <br />
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--KillWait">
        <b>slurmConfig.KillWait</b><br />
        The interval in seconds between the SIGTERM and SIGKILL signals given to a job's processes upon reaching its time limit. See the <a href="https://slurm.schedmd.com/slurm.conf.html#OPT_KillWait">slurm.conf</a> reference for more details.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        30
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--MaxNodeCount">
        <b>slurmConfig.MaxNodeCount</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        3072
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--MessageTimeout">
        <b>slurmConfig.MessageTimeout</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        100
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--MinJobAge">
        <b>slurmConfig.MinJobAge</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        300
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--MpiDefault">
        <b>slurmConfig.MpiDefault</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "pmix"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--ProctrackType">
        <b>slurmConfig.ProctrackType</b><br />
        The plugin to be used for process tracking on a job step basis. See <a href="https://slurm.schedmd.com/slurm.conf.html#OPT_ProctrackType">the Slurm documentation</a> for more details. <br /> Valid values: <ul> <li><code>proctrack/linuxproc</code></li> <li><code>proctrack/cgroup</code></li> </ul>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "proctrack/cgroup"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--Prolog">
        <b>slurmConfig.Prolog</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/usr/share/sunk/bin/prolog.sh"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--PrologFlags[0]">
        <b>slurmConfig.PrologFlags\[0]</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "Alloc"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--PrologFlags[1]">
        <b>slurmConfig.PrologFlags\[1]</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "Serial"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--RebootProgram">
        <b>slurmConfig.RebootProgram</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/usr/share/sunk/bin/reboot.sh"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--ReturnToService">
        <b>slurmConfig.ReturnToService</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        2
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SUNKJobDashboardURL">
        <b>slurmConfig.SUNKJobDashboardURL</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SUNKNodeDashboardURL">
        <b>slurmConfig.SUNKNodeDashboardURL</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SchedulerParameters[0]">
        <b>slurmConfig.SchedulerParameters\[0]</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "nohold_on_prolog_fail"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SchedulerParameters[1]">
        <b>slurmConfig.SchedulerParameters\[1]</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "max_rpc_cnt=256"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SchedulerType">
        <b>slurmConfig.SchedulerType</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sched/backfill"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SelectType">
        <b>slurmConfig.SelectType</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "select/cons_tres"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SelectTypeParameters">
        <b>slurmConfig.SelectTypeParameters</b><br />
        The values to use for the parameters of the <a href="https://slurm.schedmd.com/slurm.conf.html#OPT_SelectTypeParameters"> select/cons\_tres plugin</a>. <br /> Allowed values depend on the configured value of <code>SelectType</code>. See the <a href="https://slurm.schedmd.com/slurm.conf.html#OPT_SelectTypeParameters">slurm.conf</a> reference for more details.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "CR_CPU_MEMORY"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmSchedLogFile">
        <b>slurmConfig.SlurmSchedLogFile</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/dev/null"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmSchedLogLevel">
        <b>slurmConfig.SlurmSchedLogLevel</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        1
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmUser">
        <b>slurmConfig.SlurmUser</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "slurm"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmctldDebug">
        <b>slurmConfig.SlurmctldDebug</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "verbose"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmctldLogFile">
        <b>slurmConfig.SlurmctldLogFile</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/dev/null"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmctldParameters">
        <b>slurmConfig.SlurmctldParameters</b><br />
        The list of additional parameters to pass to slurmCtld. See <a href="https://slurm.schedmd.com/slurmctld.html">the Slurm documentation</a> for possible values.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        - idle_on_node_suspend
        - node_reg_mem_percent=95

        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmctldPidFile">
        <b>slurmConfig.SlurmctldPidFile</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/var/run/slurmctld.pid"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmctldPort">
        <b>slurmConfig.SlurmctldPort</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        6817
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmctldTimeout">
        <b>slurmConfig.SlurmctldTimeout</b><br />
        The interval, in seconds, that the backup controller waits for the primary controller to respond before assuming control. The default value is 120 seconds. May not exceed 65533.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        60
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmdDebug">
        <b>slurmConfig.SlurmdDebug</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "verbose"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmdLogFile">
        <b>slurmConfig.SlurmdLogFile</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/proc/1/fd/1"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmdPidFile">
        <b>slurmConfig.SlurmdPidFile</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/var/run/slurmd.pid"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmdPort">
        <b>slurmConfig.SlurmdPort</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        6818
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmdSpoolDir">
        <b>slurmConfig.SlurmdSpoolDir</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/var/spool/slurmd"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SlurmdTimeout">
        <b>slurmConfig.SlurmdTimeout</b><br />
        The interval, in seconds, that the Slurm controller waits for slurmd to respond before configuring that node's state to DOWN.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        60
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--StateSaveLocation">
        <b>slurmConfig.StateSaveLocation</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/var/spool/slurmctld/save"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SuspendTime">
        <b>slurmConfig.SuspendTime</b><br />
        Nodes which remain idle or down for this number of seconds will be placed into power save mode by SuspendProgram.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "INFINITE"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--SwitchType">
        <b>slurmConfig.SwitchType</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "switch/none"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--TCPTimeout">
        <b>slurmConfig.TCPTimeout</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        15
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--TaskPlugin">
        <b>slurmConfig.TaskPlugin</b><br />
        The task plugin to use. See <a href="https://slurm.schedmd.com/slurm.conf.html#OPT_TaskPlugin">the Slurm documentation</a> for more details. <br /> Multiple comma-separated values allowed. Valid values: <ul> <li><code>task/affinity</code></li> <li><code>task/cgroup</code></li> <li><code>task/none</code></li> </ul>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "task/cgroup,task/affinity"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--TaskPluginParam">
        <b>slurmConfig.TaskPluginParam</b><br />
        Optional parameters for the task plugin. See <a href="https://slurm.schedmd.com/slurm.conf.html#OPT_TaskPluginParam">the Slurm documentation</a> for more details.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "SlurmdSpecOverride"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--TopologyParam[0]">
        <b>slurmConfig.TopologyParam\[0]</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "TopoOptional"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--TopologyPlugin">
        <b>slurmConfig.TopologyPlugin</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "topology/tree"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--TreeWidth">
        <b>slurmConfig.TreeWidth</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        65533
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--UnkillableStepProgram">
        <b>slurmConfig.UnkillableStepProgram</b><br />
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "/usr/share/sunk/bin/unkillable-step.sh"
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--UnkillableStepTimeout">
        <b>slurmConfig.UnkillableStepTimeout</b><br />
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        900
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--WaitTime">
        <b>slurmConfig.WaitTime</b><br />
        Specifies how many seconds the <code>srun</code> command should wait after the first task terminates before terminating all remaining tasks. <br /> Using the <code>--wait</code> option on the <code>srun</code> command line overrides this value. The default value is <code>0</code>, which disables this feature. See the <a href="https://slurm.schedmd.com/slurm.conf.html#OPT_WaitTime">slurm.conf</a> reference for more details.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        0
        ```
      </td>
    </tr>

    <tr>
      <td id="slurmConfig--cgroupConfig">
        <b>slurmConfig.cgroupConfig</b><br />
        The <code>cgroup.conf</code> value. <br /> This is only used when <code>ProctrackType</code> is set to <code>proctrack/cgroup</code>. Note: <code>cgroup/v2</code> should be used over <code>autodetect</code> on systems using cgroup v2.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        CgroupPlugin: autodetect
        IgnoreSystemd: yes
        ConstrainCores: yes
        ConstrainDevices: yes
        ConstrainRAMSpace: yes

        ```
      </td>
    </tr>

    <tr>
      <td id="sssdContainer--enabled">
        <b>sssdContainer.enabled</b><br />
        Enable the sssd sidecar container.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="sssdContainer--livenessProbe">
        <b>sssdContainer.livenessProbe</b><br />
        The liveness probe for the sssd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="sssdContainer--readinessProbe">
        <b>sssdContainer.readinessProbe</b><br />
        The readiness probe for the sssd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="sssdContainer--startupProbe">
        <b>sssdContainer.startupProbe</b><br />
        The startup probe for the sssd container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--annotations">
        <b>syncer.annotations</b><br />
        Additional annotations for syncer resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--slurm--poolSize">
        <b>syncer.config.slurm.poolSize</b><br />
        The number of connections to be maintained in the connection pool.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        10
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--slurm--protocolVersion">
        <b>syncer.config.slurm.protocolVersion</b><br />
        The protocol version to use for communication with the Slurm controller.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "25_05"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--slurm--usePersistentConnection">
        <b>syncer.config.slurm.usePersistentConnection</b><br />
        Use Slurm's persistent connections for connection reuse.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--syncer--nodesetUpdateJobPreemption">
        <b>syncer.config.syncer.nodesetUpdateJobPreemption</b><br />
        Configuration for job preemption support. More details can be found in the [changelog](https://docs.coreweave.com/changelog/release-notes/sunk-v6-9-0#automatic-requeueing-during-rolling-upgrades)
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {
          "enabled": false,
          "method": null
        }
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--syncer--nodesetUpdateJobPreemption--enabled">
        <b>syncer.config.syncer.nodesetUpdateJobPreemption.enabled</b><br />
        Enable job preemption support.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--syncer--nodesetUpdateJobPreemption--method">
        <b>syncer.config.syncer.nodesetUpdateJobPreemption.method</b><br />
        Job preemption strategy during rolling upgrades, can be set to one of the following methods: <br /> <ul> <li><code>partition</code> Preempt jobs in specific partitions. A comma-separated list of partition names can be specified in <code>partitions</code>.</li> <li><code>qos</code> Preempt jobs based on their QoS. A comma-separated list of QoS names can be specified in <code>qos</code>.</li> <li><code>time</code> Preempt jobs if the time since the rolling delete condition has been on the pod, is greater than the set time limit. Time limit in seconds can be set in <code>timeLimit</code>.</li> </ul>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        null
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--syncer--orphanedPodDelay">
        <b>syncer.config.syncer.orphanedPodDelay</b><br />
        The delay to wait before deleting a pod that is no longer associated with a Slurm node.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "120s"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--syncer--pollInterval">
        <b>syncer.config.syncer.pollInterval</b><br />
        The polling interval for the Slurm API.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "10s"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--syncer--qosInterruptable">
        <b>syncer.config.syncer.qosInterruptable</b><br />
        The externally defined label to indicate if pod is interruptable.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "qos.coreweave.cloud/interruptable"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--syncer--reconfigureRateLimit">
        <b>syncer.config.syncer.reconfigureRateLimit</b><br />
        The rate limit, in seconds, for Slurm reconfigure requests based on additions to NodeSlices. The value must be above 0 seconds to enable this feature. Warning: if this value is too low, `scontrol reconfigure` may be executed too often, especially during periods when several nodes are newly added.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "3600s"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--config--syncer--slurmNodeCleanUp">
        <b>syncer.config.syncer.slurmNodeCleanUp</b><br />
        Removes lingering Slurm nodes from the cluster after they have been removed from their associated SUNK NodeSets.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--controllerAddress">
        <b>syncer.controllerAddress</b><br />
        The address of the Slurm controller to connect to. <br /> This should be the service address of the controller in host:port format.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        ""
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--enabled">
        <b>syncer.enabled</b><br />
        Enable the syncer. <br /> This is required for most functionality and should only be disabled for troubleshooting.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--hooksAPI">
        <b>syncer.hooksAPI</b><br />
        config for the webhooks.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {
          "nodeRebootCondition": "PhaseState",
          "nodeRebootReason": "production-powerreset",
          "safeNodeRebootCondition": "PendingPhaseState",
          "safeNodeRebootReason": "production-powerreset",
          "waitForNodeLockedInterval": "1s",
          "waitForNodeLockedTimeout": "120s"
        }
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--hooksAPI--nodeRebootCondition">
        <b>syncer.hooksAPI.nodeRebootCondition</b><br />
        Condition to indicate node should be rebooted.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "PhaseState"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--hooksAPI--nodeRebootReason">
        <b>syncer.hooksAPI.nodeRebootReason</b><br />
        The target NLCC lifecycle state associated with the `nodeRebootCondition`.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "production-powerreset"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--hooksAPI--safeNodeRebootCondition">
        <b>syncer.hooksAPI.safeNodeRebootCondition</b><br />
        Condition to indicate node should be rebooted safely.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "PendingPhaseState"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--hooksAPI--safeNodeRebootReason">
        <b>syncer.hooksAPI.safeNodeRebootReason</b><br />
        The target NLCC lifecycle state associated with the `safeNodeRebootCondition`.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "production-powerreset"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--hooksAPI--waitForNodeLockedInterval">
        <b>syncer.hooksAPI.waitForNodeLockedInterval</b><br />
        The polling interval when checking for node locked state.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "1s"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--hooksAPI--waitForNodeLockedTimeout">
        <b>syncer.hooksAPI.waitForNodeLockedTimeout</b><br />
        The timeout for checking node locked state.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "120s"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--image">
        <b>syncer.image</b><br />
        The image to use for the syncer.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        repository: registry.gitlab.com/coreweave/sunk/operator
        tag:

        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--labels">
        <b>syncer.labels</b><br />
        Additional labels for syncer resources.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        {}
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--livenessProbe">
        <b>syncer.livenessProbe</b><br />
        The liveness probe for the syncer container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        httpGet:
            path: /healthz
            port: 8081
        initialDelaySeconds: 15
        periodSeconds: 20

        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--logLevel">
        <b>syncer.logLevel</b><br />
        The log level. <br /> Uses integers or <a href="https://pkg.go.dev/go.uber.org/zap#pkg-constants">zap log level strings</a>: <ul> <li><code>debug</code></li> <li><code>info</code></li> <li><code>warn</code></li> <li><code>error</code></li> <li><code>dpanic</code></li> <li><code>panic</code></li> <li><code>fatal</code></li> </ul>
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "info"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--maxConcurrentReconciles">
        <b>syncer.maxConcurrentReconciles</b><br />
        The maximum concurrent reconciles. <br /> This should be adjusted based on the number of nodes and size of jobs launched in the Slurm cluster, to handle bursts operations quickly. A value 1/10th the number of nodes in the cluster is a good starting point for small clusters.  As cluster size increases, this value can be a smaller fraction of the total number of nodes in most cases.  For instance a value of 50 seems to handle a 2000 node cluster well.  Being too aggressive here will bottleneck on other components such as the Kubernetes API server and the Slurm controller, which in some cases may cause errors.
      </td>

      <td>int</td>

      <td>
        ```yaml wrap theme={"system"}
        50
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--nodePermissions--enabled">
        <b>syncer.nodePermissions.enabled</b><br />
        Enable node operations on the syncer, currently this allows restart of nodes when enabled.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        true
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--priorityClassName">
        <b>syncer.priorityClassName</b><br />
        The priority class name for the syncer pod.
      </td>

      <td>string</td>

      <td>
        ```yaml wrap theme={"system"}
        "sunk-control-plane"
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--readinessProbe">
        <b>syncer.readinessProbe</b><br />
        The readiness probe for the syncer container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        httpGet:
            path: /readyz
            port: 8081
        initialDelaySeconds: 5
        periodSeconds: 10

        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--resources">
        <b>syncer.resources</b><br />
        Resources for the syncer container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        limits:
            memory: 24Gi
            cpu: 16
        requests:
            cpu: 4
            memory: 24Gi

        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--startupProbe">
        <b>syncer.startupProbe</b><br />
        The startup probe for the syncer container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--watchAllNodeSets">
        <b>syncer.watchAllNodeSets</b><br />
        Watch all NodeSets in the namespace. <br /> This overrides default behavior of only watching the NodeSets deployed with this chart release.
      </td>

      <td>bool</td>

      <td>
        ```yaml wrap theme={"system"}
        false
        ```
      </td>
    </tr>

    <tr>
      <td id="syncer--watchNodeSets">
        <b>syncer.watchNodeSets</b><br />
        The list of NodeSets to watch. <br /> This overrides the default behavior of watching the NodeSets deployed with this chart release to instead watch this specific list.  This is not used if watchAllNodeSets is set to true.
      </td>

      <td>list</td>

      <td>
        ```yaml wrap theme={"system"}
        []
        ```
      </td>
    </tr>

    <tr>
      <td id="userLookupContainer--livenessProbe">
        <b>userLookupContainer.livenessProbe</b><br />
        The liveness probe for the user-lookup container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="userLookupContainer--readinessProbe">
        <b>userLookupContainer.readinessProbe</b><br />
        The readiness probe for the user-lookup container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>

    <tr>
      <td id="userLookupContainer--startupProbe">
        <b>userLookupContainer.startupProbe</b><br />
        The startup probe for the user-lookup container.
      </td>

      <td>object</td>

      <td>
        ```yaml wrap theme={"system"}
        map[]
        ```
      </td>
    </tr>
  </tbody>
</table>