-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add gke & aws auth plugins to prow images #28277
Conversation
Unknown CLA label state. Rechecking for CLA labels. Send feedback to sig-contributor-experience at kubernetes/community. /check-cla |
/approve |
We were going to switch to using a different base image. If we want to include more providers I think it makes sense to update the |
There's a lot of components that use the alpine build, either directly or through the git image. AFAICT only 4 of them need access to the build cluster and so would need the gke/aws authentication plugins. Do we still want to update all the component images? For gke-gcloud-auth-plugin, I ran into issues building for s390x. However, since I am able to build the image locally, my guess is the gcb-docker-gcloud image needs to have its docker version updated. I'll experiment locally and see if I can confirm this hypothesis |
Hmm How about modifying @dieseldesai image instead but just build amd64 and arm64 for the components that actually interact with external Kubernetes clusters? I can rename the image to We can blame the limited platform support on the tools not releasing them. |
I've got the GKE auth plugin working now for all 4 architectures: For this PR, maybe we can rebase and update the |
This can be merged now. I used @dieseldesai's image and added the aws-iam-authenticator to it. /label tide/merge-method-squash |
Were the platform issues addressed? If this change will limit the platforms supported by Prow component images we cannot merge this without more discussion as I'd expect some sort of deprecation period or a reasonable assurance that these platforms are not in use. |
Switching to these is not optional as kubectl will not work without auth plugins going forward. If people are interested in these platforms they need to go work with the auth plugin projects. |
This is ready now. The images are built successfully. I ran the cloudbuild job in my dev project. I still think we shouldn't build images for platforms that the tools don't have native builds. I found this doc helpful https://github.com/projectcalico/go-build/blob/master/README.md#cross-runnning-binaries-binfmt |
/assign @cjwagner @BenTheElder |
Well this is almost as good as an assurance that the problematic platforms are not in use. If they are in use they'll be broken soon anyways so this doesn't seem like as big of a deal. I'm a bit concerned about |
Can we verify that the gke-gcloud-auth-plugin works without the gcloud binary? It would be nice to spin up a test container and just verify if you can auth to a GKE cluster. |
Yes it does.
|
Can I get lgtm from someone please? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cjwagner, dims, upodroid The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The image failed to build :( I opened #28931 to try it again. |
Part of #28142
Part of #27896
I might run in to problems with multi-arch builds. aws-iam-authenticator doesn't have s390x and ppc64le releases :(
The google cloud sdk docker image is only available for amd64 :(
https://hub.docker.com/r/google/cloud-sdk/tags
/cc @ameukam @BenTheElder @dims
My plan is: