Skip to content
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

Multi-Arch build #48

Closed
diederichm opened this issue Aug 27, 2019 · 17 comments
Closed

Multi-Arch build #48

diederichm opened this issue Aug 27, 2019 · 17 comments
Assignees
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@diederichm
Copy link

Can you please build for s390x (and maybe ppc64 and ppc64le) ?

@colek42 colek42 mentioned this issue Nov 8, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 25, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 25, 2019
@Madhu-1
Copy link
Contributor

Madhu-1 commented Jan 2, 2020

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 2, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 1, 2020
@edmondsw
Copy link

edmondsw commented Apr 2, 2020

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 2, 2020
@ahuffman
Copy link

ahuffman commented Apr 14, 2020

Any updates on getting a multi-arch build for this? Looking for a aarch64 build specifically.

@msau42
Copy link
Collaborator

msau42 commented Apr 14, 2020

Work is in progress to migrate our build infrastructure to the build pipeline supported by wg-k8s-infra. Once we migrate there, then we can look into supporting multi-arch builds.

@msau42
Copy link
Collaborator

msau42 commented Apr 14, 2020

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Apr 14, 2020
@edmondsw
Copy link

@msau42 Thanks for the update. What is the projected timeline for that migration?

@msau42
Copy link
Collaborator

msau42 commented Apr 28, 2020

It's being actively worked on as we speak. I would expect by next month we should have something.

Also for reference, here's the suggested arches to support initially:
https://github.com/kubernetes/kubernetes/blob/master/build/pause/Makefile#L36-L54

@msau42
Copy link
Collaborator

msau42 commented Apr 28, 2020

/assign @pohly @jingxu97
cc @vitt-bagal

@edmondsw
Copy link

@msau42 excellent! Thank you!

@ruckc
Copy link

ruckc commented Aug 22, 2020

just checking on the status of this. unable to easily browse the k8s.gcr.io repositories to see if this was done for the recent releases.

@holdenk
Copy link

holdenk commented Aug 24, 2020

So I was also curious @ruckc it looks like the latest release does not yet have a multi-arch build. I ran holden@hkdesktop:~/repos/scalingpythonml/make_k8s_cluster$ docker buildx imagetools inspect k8s.gcr.io/sig-storage/csi-node-driver-registrar:v1.3.0 and I got back:

{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
   "config": {
      "mediaType": "application/vnd.docker.container.image.v1+json",
      "size": 2466,
      "digest": "sha256:37c1d9ea538b6139df2dc2807b565afed0bf47be2323ece2b83fa2d8f088ffe1"
   },
   "layers": [
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 655317,
         "digest": "sha256:9ff2acc3204b4093126adab3fed72de8f7bbfe332255b199c30b8b185fcf6923"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 7058616,
         "digest": "sha256:d0bfaf7febc5bdba655bb83e6806ed72c9017ecef71ee98871eb0ee1ddd5fdb3"
      }
   ]
}

Does anyone know of v2.0 is planned to support multi-arch builds?

@pohly
Copy link
Contributor

pohly commented Aug 24, 2020

Does anyone know of v2.0 is planned to support multi-arch builds?

Yes, they are. See kubernetes-csi/csi-release-tools#86

@msau42
Copy link
Collaborator

msau42 commented Dec 2, 2020

This should be done as of v2.0

/close

@k8s-ci-robot
Copy link
Contributor

@msau42: Closing this issue.

In response to this:

This should be done as of v2.0

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

dobsonj pushed a commit to dobsonj/node-driver-registrar that referenced this issue Oct 17, 2023
OCPBUGS-16608: [release-4.13] UPSTREAM: 284: Bump golang.org/x/net
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests