Marko Mudrinić

/test pull-machine-controller-e2e-aws

/test pull-machine-controller-e2e-aws

/test all

/test pull-machine-controller-e2e-ubuntu-upgrade /test pull-machine-controller-e2e-aws /test pull-machine-controller-e2e-aws-arm /test pull-machine-controller-e2e-aws-ebs-encryption-enabled /test pull-machine-controller-e2e-aws-spot-instance /test pull-machine-controller-e2e-openstack /test pull-machine-controller-e2e-openstack-project-auth

/remove-lifecycle stale

/close

I have to echo what @BenTheElder said. All projects living under the Kubernetes umbrella, i.e. in the Kubernetes GitHub organizations, should use the community infrastructure for their purposes, unless instructed...

Also, let's not forget the situation that we had with vSphere-related projects just a couple of weeks ago, where the registry simply went missing: https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/3053 We want to make sure...