Mirror registry deprecation for containerd 1.5

kubermatic / kubeone

Kubermatic KubeOne automate cluster operations on all your cloud, on-prem, edge, and IoT environments.

https://kubeone.io

Apache License 2.0

1.38k stars 234 forks source link

Mirror registry deprecation for containerd 1.5 #2076

Open mate4st opened 2 years ago

mate4st commented 2 years ago

registry.mirrors and registry.configs has been DEPRECATED in containerd v1.5.

We need to upgrade the configuration of containerd to be conformant with the new handling of registries.

https://github.com/containerd/containerd/blob/release/1.5/docs/cri/config.md

### Tasks
- [x] Check containerd v2 for any breaking API changes
- [x] Upgrade to the latest available 1.x version
- [ ] Migrate to the new config format available in 1.7+

kron4eg commented 2 years ago

While it's DEPRECATED, it still works. We don't need to upgrade before we upgrade to containerd 1.6. We tightly control the minor version of containerd. This issue can be closed.

xmudrii commented 2 years ago

This issue can be closed.

I would leave it open. This is something we need to tackle in (near) future. Having an issue is helpful to track and plan/prioritize it accordingly.

kubermatic-bot commented 2 years ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

embik commented 2 years ago

/remove-lifecycle stale

kubermatic-bot commented 1 year ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kron4eg commented 1 year ago

/remove-lifecycle stale

kubermatic-bot commented 1 year ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kron4eg commented 1 year ago

/remove-lifecycle stale

kubermatic-bot commented 1 year ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kron4eg commented 1 year ago

/remove-lifecycle stale

kubermatic-bot commented 1 year ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

xmudrii commented 1 year ago

This might affect us for containerd 1.7, so we should double-check. /remove-lifecycle stale

kubermatic-bot commented 11 months ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

xmudrii commented 11 months ago

/remove-lifecycle stale

kubermatic-bot commented 8 months ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kron4eg commented 8 months ago

/remove-lifecycle stale

kubermatic-bot commented 5 months ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

xmudrii commented 5 months ago

/remove-lifecycle stale