- The packages `iw` and `wirelesstools` (`iwconfig`, `iwlist`, etc.) are no longer installed implicitly if wireless networking has been enabled.
- The Traefik module now features new ways to deploy the dynamic and static configuration files. Move your existing declarative static and dynamic configurations to `services.traefik.static.settings` and `services.traefik.dynamic.files."my-application".settings` respectively. The `services.traefik.dynamic.settings` option is available for a simpler migration without needing to define a filename like `my-application`, but this option will be removed in NixOS 26.11.
-`services.kubernetes.addons.dns.coredns` has been renamed to `services.kubernetes.addons.dns.corednsImage` and now expects a
package instead of attrs. Now, by default, nixpkgs.coredns in conjunction with dockerTools.buildImage is used, instead
of pulling the upstream container image from Docker Hub. If you want the old behavior, you can set:
(Using that option has precedence over `dynamicConfigOptions`)
Path to the directory Traefik should watch for configuration files.
::: {.warning}
Files in this directory matching the glob `_nixos-*` (reserved for Nix-managed dynamic configurations) will be deleted as part of
`systemd-tmpfiles-resetup.service`, _**regardless of their origin.**_.
:::
'';
};
files=mkOption{
type=attrsOf(submodule{
options.settings=mkOption{
type=format.type;
description=''
Dynamic configuration for Traefik, written in Nix.
dynamicConfigOptions=mkOption{
::: {.note}
This will be serialized to JSON (which is considered valid YAML) at build, and passed as part of the static file.
:::
'';
example={
http.routers."api"={
service="api@internal";
rule="Host(`localhost`)";
};
};
};
});
default={};
example={
"dashboard".settings={
http.routers."api"={
service="api@internal";
rule="Host(`198.51.100.1`)";
};
};
};
description=''
Dynamic configuration for Traefik.
Dynamic configuration files to write. These are symlinked in `services.traefik.dynamic.dir` upon activation,
allowing configuration to be upated without restarting the primary daemon.
::: {.note}
Due to [a limitation in Traefik](https://github.com/traefik/traefik/issues/10890); any syntax error in a dynamic configuration will cause the _**entire file provider**_ to be ignored.
This may cause interuption in service, which may include access to the Traefik dashboard, if [enabled and configured](https://doc.traefik.io/traefik/operations/dashboard).
:::
'';
};
# TODO: Drop in 26.11.
settings=mkOption{
type=format.type;
description=''
Dynamic configuration for Traefik, written in Nix.
This option is intended for easily migrating pre-26.05 Traefik configurations, and will be removed in NixOS 26.11.
::: {.note}
Configurations added here will be translated into a file for {option}`services.traefik.dynamic.files`, named `custom-migrated`.
Location for any persistent data traefik creates, ie. acme
Location for any persistent data Traefik creates, such as the ACME certificate store.
::: {.note}
If left as the default value, this directory will automatically be created
before the Traefik server starts, otherwise you are responsible for ensuring
the directory exists with appropriate ownership and permissions.
:::
'';
};
group=mkOption{
user=mkOption{
default="traefik";
type=types.str;
example="docker";
type=str;
description=''
Set the group that traefik runs under.
For the docker backend this needs to be set to `docker` instead.
User under which Traefik runs.
::: {.note}
If left as the default value this user will automatically be created
on system activation, otherwise you are responsible for
ensuring the user exists before the Traefik service starts.
:::
'';
};
package=mkPackageOptionpkgs"traefik"{};
group=mkOption{
default="traefik";
type=str;
description=''
Primary group under which Traefik runs.
For the Docker backend, use {option}`services.traefik.supplementaryGroups` instead of overriding this option.
::: {.note}
If left as the default value this group will automatically be created
on system activation, otherwise you are responsible for
ensuring the group exists before the Traefik service starts.
:::
'';
};
supplementaryGroups=mkOption{
default=[];
type=listOfstr;
example=["docker"];
description=''
Additional groups under which Traefik runs.
This can be used to give additional permissions, such as the group required by the `docker` provider.
::: {.note}
With the `docker` provider, Traefik manages connection to containers via the Docker socket,
which requires membership of the `docker` group for write access.
:::
'';
};
environmentFiles=mkOption{
default=[];
type=types.listOftypes.path;
type=listOfpath;
example=["/run/secrets/traefik.env"];
description=''
Files to load as environment file. Environment variables from this file
will be substituted into the static configuration file using envsubst.
Files to load as an environment file just before Traefik starts.
This can be used to pass secrets such as [DNS challenge API tokens](https://doc.traefik.io/traefik/https/acme/#providers) or [EAB credentials](https://doc.traefik.io/traefik/reference/static-configuration/env/).
Whether to use `envSubst` in the `ExecStartPre` phase to augment the generated static config. See {option}`services.traefik.environmentFiles`.
::: {.note}
If you use environment files with Traefik but *do not* utilise environment variables in the static config, this can safely be disabled to reduce startup time.
