Sascha Grunert e89547d308 Check for all errors in CRI connection validation ... We only have one CRI API (v1) to validate during the initial connection of the kubelet with the container runtime. Therefore we can now verify all kind of GRPC related issues. Fixes: https://github.com/kubernetes/kubernetes/issues/114956 Signed-off-by: Sascha Grunert <sgrunert@redhat.com>		2023-01-17 09:24:31 +01:00
..
fake	Add fake runtimes and CRI changes for KEP-2371	2022-11-08 14:47:08 -05:00
doc.go
OWNERS	Check in OWNERS modified by update-yamlfmt.sh	2021-12-09 21:31:26 -05:00
remote_image_test.go	Second attempt: Plumb context to Kubelet CRI calls (#113591)	2022-11-05 06:02:13 -07:00
remote_image.go	Check for all errors in CRI connection validation	2023-01-17 09:24:31 +01:00
remote_runtime_test.go	Second attempt: Plumb context to Kubelet CRI calls (#113591)	2022-11-05 06:02:13 -07:00
remote_runtime.go	Check for all errors in CRI connection validation	2023-01-17 09:24:31 +01:00
utils_test.go	Make CRI v1 the default and allow a fallback to v1alpha2	2021-11-17 11:05:05 -08:00
utils.go	Second attempt: Plumb context to Kubelet CRI calls (#113591)	2022-11-05 06:02:13 -07:00