-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Containerd CRI registry mirrors and configs config via config.toml have been deprecated #8972
Comments
$ sudo cat /etc/containerd/config.toml
$ sudo journalctl -u k3s | grep -i "config.toml"
OLD vs NEW (showing new config path entry) $ cat old-format.toml
$ cat config.toml
|
##Environment Details Infrastructure
Node(s) CPU architecture, OS, and version:
Cluster Configuration:
Config.yaml:
Validation
$ sudo cat /var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl
$ sudo INSTALL_K3S_VERSION=v1.29.1-rc2+k3s1 INSTALL_K3S_EXEC=server ./install-k3s.sh
$ set_kubefig //export KUBECONFIG=/etc/rancher/k3s/k3s.yaml $ kg runtimeclass
|
Newer release of containerd have deprecated use of config.toml to configure registry endpoints and TLS config, in favor of docker-style
certs.d
directory structure. See the comment at https://github.com/containerd/containerd/blob/release/1.7/docs/cri/registry.mdOther projects like https://github.com/XenitAB/spegel require use of this structure.
There are other benefits to this, such as allowing for dynamic reloading of config other than auth, which is still only available via config.toml.
There are other issues also open tracking this work:
config_path
: On-the-fly container registry configuration #5568The text was updated successfully, but these errors were encountered: