Configuration reference does not have clustermode settings

[pwonson]

Describe the bug The configuration reference is missing the cluster mode settings: Cluster Mode settings

# Heartbeat
# Frequency of heartbeat message in seconds
rundeck.clusterMode.heartbeat.interval=30
# Start up delay in seconds before heartbeat messages begin
rundeck.clusterMode.heartbeat.delay=10
# Other member status
# Seconds since last heartbeat from another member to consider it inactive
rundeck.clusterMode.heartbeat.considerInactive=150
# Seconds since last heartbeat from another member to consider it offline
rundeck.clusterMode.heartbeat.considerDead=300
# Automatic takeover of retries of offline members
# Enable automatic cleanup of stale jobs for an offline member
rundeck.clusterMode.recoverExecutions.enabled=true
# Mark job execution incomplete after a member goes offline 
rundeck.clusterMode.recoverExecutions.process.interval=10
# Members for which this instance recovers executions
# if static, 'allowed' setting required
rundeck.clusterMode.recoverExecutions.policy=Any
# (optional for static) Members for which this instance can takeover retries 
# rundeck.clusterMode.recoverExecutions.allowed=<UUID>
# Delay in seconds to wait after sending autoretry proposal
rundeck.clusterMode.recoverExecutions.delay=30
# Delay in seconds before doing another autoretry of the same member
rundeck.clusterMode.recoverExecutions.sleep=60
# Automatic takeover of schedules for offline members
# Enables automatic takeover of schedules owned by an offline member
rundeck.clusterMode.autotakeover.enabled=true
# Members for which this instance can takeover schedules
rundeck.clusterMode.autotakeover.policy=any
# (optional for static) Members for which this instance can takeover retries 
# rundeck.clusterMode.autotakeover.allowed=<UUID>
# Delay in seconds to wait after sending auto takeover proposal
rundeck.clusterMode.autotakeover.delay = 60
# Delay in seconds before doing another autotakeover of the same member
rundeck.clusterMode.autotakeover.sleep = 300
# Running job executions
# Policy that determines where a job executes
rundeck.clusterMode.remoteExecution.policy = Load
# Member that executes jobs triggered locally 
rundeck.clusterMode.remoteExecution.config.allowed = Self,Other
# Further restricts Other by member tags set in framework.properties
# rundeck.clusterMode.remoteExecution.config.allowedTags = <TAGS>
# rundeck.clusterMode.remoteExecution.config.preferredTags = <TAGS>
# Status of member where job execution is sent
rundeck.clusterMode.remoteExecution.config.activeOnly = true
# (Load only) Member selection criteria
rundeck.clusterMode.remoteExecution.config.criteria = threadRatio,load
# (Load only) Weight of selection criteria
rundeck.clusterMode.remoteExecution.config.weights = 1.0,1.5
# Number of groups is determined number of weights in list
# Selection is by weight -- if there are four rundeck instances
# least busy instances would be put in group one and all jobs triggered 
# at a given time would be sent to the first group
rundeck.clusterMode.remoteExecution.config.groupWeight=2,0
# Send jobs with secure options to remote members
rundeck.clusterMode.messaging.encryption.enabled=true

Source page Section should be included here: https://docs.rundeck.com/docs/administration/configuration/