Akihiro Suda 1b3a96da6c cri: propagate deprecation list to runtime status ... Propagate the deprecation list to CRI runtime conditions. The propagated conditions are visible via `crictl info`, but not visible via `kubectl get nodes -o yaml` yet, although the CRI API says "These conditions will be exposed to users to help them understand the status of the system". https://github.com/kubernetes/cri-api/blob/v0.29.1/pkg/apis/runtime/v1/api.proto#L1505-L1509 Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>		2024-02-14 03:59:49 +09:00
..
config_kernel_linux_test.go	Move CRI from pkg/ to internal/	2024-02-02 10:12:08 -08:00
config_kernel_linux.go	Revert "cri: make read-only mounts recursively read-only"	2024-02-04 01:17:14 +09:00
config_kernel_other.go	Revert "cri: make read-only mounts recursively read-only"	2024-02-04 01:17:14 +09:00
config_test.go	Revert "cri: make read-only mounts recursively read-only"	2024-02-04 01:17:14 +09:00
config_unix.go	Move CRI from pkg/ to internal/	2024-02-02 10:12:08 -08:00
config_windows.go	Move CRI from pkg/ to internal/	2024-02-02 10:12:08 -08:00
config.go	cri: propagate deprecation list to runtime status	2024-02-14 03:59:49 +09:00
streaming_test.go	Move CRI from pkg/ to internal/	2024-02-02 10:12:08 -08:00
streaming.go	Move CRI from pkg/ to internal/	2024-02-02 10:12:08 -08:00