-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs and Changelog catch up #7010
Conversation
fd6127f
to
fe55b5a
Compare
@@ -98,6 +98,13 @@ server { | |||
deployment must be in the terminal state before it is eligible for garbage | |||
collection. This is specified using a label suffix like "30s" or "1h". | |||
|
|||
- `default_scheduler_config` <code>([scheduler_configuration][update-scheduler-config]: | |||
nil)</code> - Specifies the initial default scheduler config when | |||
bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when bootstrapping a cluster
Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor typo
bootstrapping cluster. The parameter is ignored once the cluster is bootstrapped or | ||
value is updated through the [API endpoint][update-scheduler-config]. See [the | ||
example section](#configuring-scheduler-config) for more details | ||
`default_scheduler_config` was introduced in Nomad 0.11.4. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nomad 0.10.4
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Batch update of my changes for the last month 😅 .