config-fcos-v1_0.md

title	parent	nav_order
Fedora CoreOS v1.0.0	Configuration specifications	49

Fedora CoreOS Specification v1.0.0

The Fedora CoreOS configuration is a YAML document conforming to the following specification, with italicized entries being optional:

• variant (string): used to differentiate configs for different operating systems. Must be fcos for this specification.
• version (string): the semantic version of the spec for this document. This document is for version 1.0.0 and generates Ignition configs with version 3.0.0.
• ignition (object): metadata about the configuration itself.
  • config (object): options related to the configuration.
    • merge (list of objects): a list of the configs to be merged to the current config.
      • source (string): the URL of the config. Supported schemes are http, https, tftp, s3, and data. When using http, it is advisable to use the verification option to ensure the contents haven't been modified.
      • verification (object): options related to the verification of the config.
        • hash (string): the hash of the config, in the form <type>-<value> where type is sha512.
    • replace (object): the config that will replace the current.
      • source (string): the URL of the config. Supported schemes are http, https, tftp, s3, and data. When using http, it is advisable to use the verification option to ensure the contents haven't been modified.
      • verification (object): options related to the verification of the config.
        • hash (string): the hash of the config, in the form <type>-<value> where type is sha512.
  • timeouts (object): options relating to http timeouts when fetching files over http or https.
    • http_response_headers (integer): the time to wait (in seconds) for the server's response headers (but not the body) after making a request. 0 indicates no timeout. Default is 10 seconds.
    • http_total (integer): the time limit (in seconds) for the operation (connection, request, and response), including retries. 0 indicates no timeout. Default is 0.
  • security (object): options relating to network security.
    • tls (object): options relating to TLS when fetching resources over https.
      • certificate_authorities (list of objects): the list of additional certificate authorities (in addition to the system authorities) to be used for TLS verification when fetching over https. All certificate authorities must have a unique source.
        • source (string): the URL of the certificate bundle (in PEM format). The bundle can contain multiple concatenated certificates. Supported schemes are http, https, tftp, s3, and data. When using http, it is advisable to use the verification option to ensure the contents haven't been modified.
        • verification (object): options related to the verification of the certificate bundle.
          • hash (string): the hash of the certificate bundle, in the form <type>-<value> where type is sha512.
• storage (object): describes the desired state of the system's storage devices.
  • disks (list of objects): the list of disks to be configured and their options. Every entry must have a unique device.
    • device (string): the absolute path to the device. Devices are typically referenced by the /dev/disk/by-* symlinks. The boot disk can be referenced as /dev/disk/by-id/coreos-boot-disk.
    • wipe_table (boolean): whether or not the partition tables shall be wiped. When true, the partition tables are erased before any further manipulation. Otherwise, the existing entries are left intact.
    • partitions (list of objects): the list of partitions and their configuration for this particular disk. Every partition must have a unique number, or if 0 is specified, a unique label.
      • label (string): the PARTLABEL for the partition.
      • number (integer): the partition number, which dictates its position in the partition table (one-indexed). If zero, use the next available partition slot.
      • size_mib (integer): the size of the partition (in mebibytes). If zero, the partition will be made as large as possible.
      • start_mib (integer): the start of the partition (in mebibytes). If zero, the partition will be positioned at the start of the largest block available.
      • type_guid (string): the GPT partition type GUID. If omitted, the default will be 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem data).
      • guid (string): the GPT unique partition GUID.
      • wipe_partition_entry (boolean): if true, Ignition will clobber an existing partition if it does not match the config. If false (default), Ignition will fail instead.
      • should_exist (boolean): whether or not the partition with the specified number should exist. If omitted, it defaults to true. If false Ignition will either delete the specified partition or fail, depending on wipePartitionEntry. If false number must be specified and non-zero and label, start, size, guid, and typeGuid must all be omitted.
  • raid (list of objects): the list of RAID arrays to be configured. Every RAID array must have a unique name.
    • name (string): the name to use for the resulting md device.
    • level (string): the redundancy level of the array (e.g. linear, raid1, raid5, etc.).
    • devices (list of strings): the list of devices (referenced by their absolute path) in the array.
    • spares (integer): the number of spares (if applicable) in the array.
    • options (list of strings): any additional options to be passed to mdadm.
  • filesystems (list of objects): the list of filesystems to be configured. device and format need to be specified. Every filesystem must have a unique device.
    • device (string): the absolute path to the device. Devices are typically referenced by the /dev/disk/by-* symlinks.
    • format (string): the filesystem format (ext4, btrfs, xfs, vfat, or swap).
    • path (string): the mount-point of the filesystem while Ignition is running relative to where the root filesystem will be mounted. This is not necessarily the same as where it should be mounted in the real root, but it is encouraged to make it the same.
    • wipe_filesystem (boolean): whether or not to wipe the device before filesystem creation, see Ignition's documentation on filesystems for more information. Defaults to false.
    • label (string): the label of the filesystem.
    • uuid (string): the uuid of the filesystem.
    • options (list of strings): any additional options to be passed to the format-specific mkfs utility.
  • files (list of objects): the list of files to be written. Every file, directory and link must have a unique path.
    • path (string): the absolute path to the file.
    • overwrite (boolean): whether to delete preexisting nodes at the path. contents must be specified if overwrite is true. Defaults to false.
    • contents (object): options related to the contents of the file.
      • source (string): the URL of the file. Supported schemes are http, https, tftp, s3, and data. When using http, it is advisable to use the verification option to ensure the contents haven't been modified. If source is omitted and a regular file already exists at the path, Ignition will do nothing. If source is omitted and no file exists, an empty file will be created. Mutually exclusive with inline.
      • inline (string): the contents of the file. Mutually exclusive with source.
      • compression (string): the type of compression used on the file (null or gzip). Compression cannot be used with S3.
      • verification (object): options related to the verification of the file.
        • hash (string): the hash of the file, in the form <type>-<value> where type is sha512. If compression is specified, the hash describes the decompressed file.
    • append (list of objects): list of fragments to be appended to the file. Follows the same structure as contents.
      • source (string): the URL of the fragment. Supported schemes are http, https, tftp, s3, and data. When using http, it is advisable to use the verification option to ensure the contents haven't been modified. Mutually exclusive with inline.
      • inline (string): the contents of the fragment. Mutually exclusive with source.
      • compression (string): the type of compression used on the fragment (null or gzip). Compression cannot be used with S3.
      • verification (object): options related to the verification of the fragment.
        • hash (string): the hash of the fragment, in the form <type>-<value> where type is sha512. If compression is specified, the hash describes the decompressed fragment.
    • mode (integer): the file's permission mode. Setuid/setgid/sticky bits are not supported. If not specified, the permission mode for files defaults to 0644 or the existing file's permissions if overwrite is false, contents is unspecified, and a file already exists at the path.
    • user (object): specifies the file's owner.
      • id (integer): the user ID of the owner.
      • name (string): the user name of the owner.
    • group (object): specifies the file's group.
      • id (integer): the group ID of the group.
      • name (string): the group name of the group.
  • directories (list of objects): the list of directories to be created. Every file, directory, and link must have a unique path.
    • path (string): the absolute path to the directory.
    • overwrite (boolean): whether to delete preexisting nodes at the path. If false and a directory already exists at the path, Ignition will only set its permissions. If false and a non-directory exists at that path, Ignition will fail. Defaults to false.
    • mode (integer): the directory's permission mode. Setuid/setgid/sticky bits are not supported. If not specified, the permission mode for directories defaults to 0755 or the mode of an existing directory if overwrite is false and a directory already exists at the path.
    • user (object): specifies the directory's owner.
      • id (integer): the user ID of the owner.
      • name (string): the user name of the owner.
    • group (object): specifies the directory's group.
      • id (integer): the group ID of the group.
      • name (string): the group name of the group.
  • links (list of objects): the list of links to be created. Every file, directory, and link must have a unique path.
    • path (string): the absolute path to the link
    • overwrite (boolean): whether to delete preexisting nodes at the path. If overwrite is false and a matching link exists at the path, Ignition will only set the owner and group. Defaults to false.
    • user (object): specifies the owner for a symbolic link. Ignored for hard links.
      • id (integer): the user ID of the owner.
      • name (string): the user name of the owner.
    • group (object): specifies the group for a symbolic link. Ignored for hard links.
      • id (integer): the group ID of the group.
      • name (string): the group name of the group.
    • target (string): the target path of the link
    • hard (boolean): a symbolic link is created if this is false, a hard one if this is true.
• systemd (object): describes the desired state of the systemd units.
  • units (list of objects): the list of systemd units. Every unit must have a unique name.
    • name (string): the name of the unit. This must be suffixed with a valid unit type (e.g. "thing.service").
    • enabled (boolean): whether or not the service shall be enabled. When true, the service is enabled. When false, the service is disabled. When omitted, the service is unmodified. In order for this to have any effect, the unit must have an install section.
    • mask (boolean): whether or not the service shall be masked. When true, the service is masked by symlinking it to /dev/null. When false, the service is unmasked by deleting the symlink to /dev/null if it exists.
    • contents (string): the contents of the unit.
    • dropins (list of objects): the list of drop-ins for the unit. Every drop-in must have a unique name.
      • name (string): the name of the drop-in. This must be suffixed with ".conf".
      • contents (string): the contents of the drop-in.
• passwd (object): describes the desired additions to the passwd database.
  • users (list of objects): the list of accounts that shall exist. All users must have a unique name.
    • name (string): the username for the account.
    • password_hash (string): the hashed password for the account.
    • ssh_authorized_keys (list of strings): a list of SSH keys to be added as an SSH key fragment at .ssh/authorized_keys.d/ignition in the user's home directory. All SSH keys must be unique.
    • uid (integer): the user ID of the account.
    • gecos (string): the GECOS field of the account.
    • home_dir (string): the home directory of the account.
    • no_create_home (boolean): whether or not to create the user's home directory. This only has an effect if the account doesn't exist yet.
    • primary_group (string): the name of the primary group of the account.
    • groups (list of strings): the list of supplementary groups of the account.
    • no_user_group (boolean): whether or not to create a group with the same name as the user. This only has an effect if the account doesn't exist yet.
    • no_log_init (boolean): whether or not to add the user to the lastlog and faillog databases. This only has an effect if the account doesn't exist yet.
    • shell (string): the login shell of the new account.
    • system (boolean): whether or not this account should be a system account. This only has an effect if the account doesn't exist yet.
  • groups (list of objects): the list of groups to be added. All groups must have a unique name.
    • name (string): the name of the group.
    • gid (integer): the group ID of the new group.
    • password_hash (string): the hashed password of the new group.
    • system (boolean): whether or not the group should be a system group. This only has an effect if the group doesn't exist yet.