Ole Markus With
Ole Markus With
You probably need to run `./hack/update-expected.sh` to fix the tests.
The issue is indeed the same. When kubelet initiates a container pull, it will use the ECR plugin and pass this on to containerd. Containerd has no knowledge of neither...
I think we can promote v1alpha2 to v1. It just seems silly to have a stable product use alpha API versions that are really of v1 quality. I think perhaps...
As mentioned in the PR, arm64 is already supported and published together with the amd64 images.
I think these are good suggestions, but probably hard to prioritise for most of the maintainers. It should however be low-hanging fruit for new contributors.
Thanks for that. I suggest writing user-facing text directly to stdout and not go through klog. The remaining klog lines could go through `-v2`.
The information that users should read should just be outputted with `fmt.Printf()`. The things that are less useful should use e.g `klog.V(2).Infof()`.
Feature-wise I think these are good points. I also think we need some criterias around * active maintainers * access to dev environments