Mahamed Ali

We should bump them together, the assumption was they were in the same repo but we split them up.

Fixed in https://github.com/kubernetes/test-infra/pull/34993

Try to follow the approach that we do for archeio(registry.k8s.io). We build an image, publish it and then update the terraform code to use that revision.

Hi @medyagh I'm a fellow SIG Infra/Testing maintainer with several comments to share. At a high level, I recommend you rewrite the Minikube CI and release pipelines to fully use...

> I feel like this discussion would be better to do over a call, would you guys be open to discuss ? Lets discuss it further in a call. >...

> SSHing into a GCE instance would still need a GCP Project for minikube owned by community (the purpose of this issue) It doesn't, we have something called boskos and...

That's correct, there should be no differences between the images. You should be able to promote any staging image to production right away.

This PR needs to be tweaked, I'll open a new one with the correct changes

Please publish your images to `us-central1-docker.pkg.dev/k8s-staging-images/aws-encryption-provider` Thanks

/ok-to-test