Skip to content

mvaictl nodegroup create

Create a nodegroup

mvaictl nodegroup create NAME [flags]

Examples

  # Create a nodegroup with one or multiple nodes
  mvaictl nodegroup create my-nodegroup --node node1
  mvaictl nodegroup create my-nodegroup --node node1 --node node2

  # Create a nodegroup with fractional GPU enabled
  mvaictl nodegroup create my-nodegroup --node node1 --fractional-gpu

  # Create a nodegroup under a department that is not the current context’s department
  mvaictl nodegroup create my-nodegroup --node node1 --department my-department

Options

      --node stringArray               The names of nodes belonging to this nodegroup
      --department string              Department that this nodegroup belongs to (default to the department in the current context)
      --fractional-gpu                 Enable fractional GPU on this nodegroup (default false)
      --show-managed-fields            If true, keep the managedFields when printing objects in JSON or YAML format.
      --template string                Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [http://golang.org/pkg/text/template/#pkg-overview].
      --allow-missing-template-keys    If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (default true)
  -o, --output string                  Output format. One of: (json, yaml, name, go-template, go-template-file, template, templatefile, jsonpath, jsonpath-as-json, jsonpath-file).
      --save-config                    If true, the configuration of current object will be saved in its annotation. Otherwise, the annotation will be unchanged. This flag is useful when you want to perform kubectl apply on this object in the future.
      --validate string[="strict"]     Must be one of: strict (or true), warn, ignore (or false). "true" or "strict" will use a schema to validate the input and fail the request if invalid. It will perform server side validation if ServerSideFieldValidation is enabled on the api-server, but will fall back to less reliable client-side validation if not. "warn" will warn about unknown or duplicate fields without blocking the request if server-side field validation is enabled on the API server, and behave as "ignore" otherwise. "false" or "ignore" will not perform any schema validation, silently dropping any unknown or duplicate fields. (default "strict")
      --dry-run string[="unchanged"]   Must be "none", "server", or "client". If client strategy, only print the object that would be sent, without sending it. If server strategy, submit server-side request without persisting the resource. (default "none")
      --field-manager string           Name of the manager used to track field ownership. (default "mvaictl-create")
  -h, --help                           help for create

Options inherited from parent commands

  -c, --config string        Path to mvaictl config directory (default "~/.mvaictl")
      --warnings-as-errors   Treat warnings received from the server as errors and exit with a non-zero exit code

SEE ALSO