HNC: Provide multiarch images (e.g. arm64)

[DWSR]

Hey all, I'd like to use HNC with my ARM cluster, but can't because HNC doesn't provide ARM images (that I can see).

Not sure how much work this would be, but would definitely help those of us running on e.g. AWS Graviton or Raspberry Pis.

[adrianludwin]

Interesting. I'd love to support ARM but I'm not sure how to create a multiarch image and (much more importantly) I have no way of testing it since I don't have access to an ARM cluster. Are you able to provide a PR and test it on your cluster?

…

On Tue, Feb 9, 2021 at 8:35 PM Brandon McNama ***@***.***> wrote: Hey all, I'd like to use HNC with my ARM cluster, but can't because HNC doesn't provide ARM images (that I can see). Not sure how much work this would be, but would definitely help those of us running on e.g. AWS Graviton or Raspberry Pis. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1383>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE43PZB534I2AORQK2MZGUTS6HPFZANCNFSM4XMBRXJQ> .

[DWSR]

@adrianludwin This is relatively straightforward to build with buildx. I haven't done it with CloudBuild before, but it appears that someone else has: https://hub.docker.com/r/harshavardhanj/docker-buildx. I don't have easy access to a GCP account for CloudBuild, though.

Regarding testing, GCP (and thus GKE) doesn't appear to have any ARM support, so that would be a pretty major change. I'm happy to test it against my home Pi cluster to get an image out the door, but that's obviously not a reasonable approach moving forward.

How are images for e.g. kube-proxy and other Control Plane components tested for various architectures?

[adrianludwin]

I'm not sure how the other components are tested - most testing is on GCP, which as you say, only has Intel and AMD support. I'd be comfortable using a build process that only got tested once, as long as we stated clearly that this is the case (this is what we do with macOS support for kubectl-hns). As for Cloud Build, if you sign up for a GCP account, you get 120 free build-minutes of Cloud Build a day <https://cloud.google.com/build/pricing> on an e2-medium. That should be enough to test, since HNC typically builds in well under 5 minutes. Sorry I don't have the time to look into this myself. I know ARM is getting more common as a target for GKE so I'm sure someone will get to it at some point, but right now I don't have the time or ability to look into it. If you can get something working on your test account I'll be happy to merge it (after a few questions) but if not, I'm going to have to wait until GCP customers are asking for it (e.g. Anthos on-prem) or someone else is able to submit a PR. Sorry about that!

…

On Tue, Feb 9, 2021 at 10:58 PM Brandon McNama ***@***.***> wrote: @adrianludwin <https://github.com/adrianludwin> This is relatively straightforward to build with buildx ***@***.***/building-multi-architecture-docker-images-with-buildx-27d80f7e2408>. I haven't done it with CloudBuild before, but it appears that someone else has: https://hub.docker.com/r/harshavardhanj/docker-buildx. I don't have easy access to a GCP account for CloudBuild, though. Regarding testing, GCP (and thus GKE) doesn't appear to have any ARM support, so that would be a pretty major change. I'm happy to test it against my home Pi cluster to get an image out the door, but that's obviously not a reasonable approach moving forward. How are images for e.g. kube-proxy and other Control Plane components tested for various architectures? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1383 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE43PZANURRYLJMMCROSL7DS6H76HANCNFSM4XMBRXJQ> .

[fejta-bot]

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-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

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-contributor-experience at kubernetes/community.
/lifecycle rotten

[DWSR]

/remove-lifecycle rotten

[adrianludwin]

This issue has moved to kubernetes-sigs/hierarchical-namespaces#21. Closing this copy.

/close

[k8s-ci-robot]

@adrianludwin: Closing this issue.

In response to this:

This issue has moved to kubernetes-sigs/hierarchical-namespaces#21. Closing this copy.

/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.