Skip to content
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 deprecated CRI hosts config #2875

Open
BenTheElder opened this issue Aug 10, 2022 · 3 comments
Open

containerd deprecated CRI hosts config #2875

BenTheElder opened this issue Aug 10, 2022 · 3 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.

Comments

@BenTheElder
Copy link
Member

This is unfortunate, it will be much harder for users to configure things like local registry as you cannot configure it inline in containerd config anymore. Also, enabling the new non-deprecated configuration route will disable the old one AFAICT https://github.com/containerd/containerd/blob/main/docs/hosts.md#cri

You now need to create a directory with a host.toml file for each host, I'm also not sure if this means wildcard hosts are no longer supported.

see also: kubernetes/kubernetes#110312

@BenTheElder
Copy link
Member Author

#3233 Is out to give us a chance to pivot the default but it will be some time before user configs have this.

I think we're going to need a PSA in the next round of release notes

@BenTheElder BenTheElder self-assigned this May 19, 2023
@BenTheElder
Copy link
Member Author

This is going to be a bit kludge without more functionality. I guess we can eventually flip on the config path and then tell users to extraMounts a directory with the host configs but that's not amazing and it's more error prone than the existing approach (commonly users don't have the right mount sharing)

@BenTheElder
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.
Projects
None yet
Development

No branches or pull requests

1 participant