Apple Silicon/M1 builds for Istioctl

[cagataygurturk]

Describe the feature request

Native builds for Apple Silicon/M1 after Go releases its support for that platform.

Describe alternatives you've considered

Currently Rosetta 2 runs Istioctl just fine.

[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[x] Test and Release
[x] User Experience
[ ] Developer Infrastructure

[howardjohn]

If I understand correctly, this requires go 1.16 (https://tip.golang.org/doc/go1.16#darwin) then building with GOOS=darwin and GOARCH=arm64. This is reasonable to do once we update to 1.16, which we will do once its released, which will probably just miss the 1.9 release.

[cagataygurturk]

That‘s correct @howardjohn. The relevant Go issue tracking Apple Silicon support is here: golang/go#39782

Can we protect this issue being closed for being stale, since Go support will at least take until February 2021 to be released?

[brian-avery]

Changed this to a p1 in 1.10 due to the fact that this already works in Rosetta and won't make it into 1.9. Having builds will be important, but we also don't have a way to test this. Are there any volunteers? Thanks.

[cagataygurturk]

Changed this to a p1 in 1.10 due to the fact that this already works in Rosetta and won't make it into 1.9. Having builds will be important, but we also don't have a way to test this. Are there any volunteers? Thanks.

I own an M1 and I am happy to help for manually testing at least :)

[cagataygurturk]

Go 1.16 is released

[howardjohn]

@cagataygurturk would appreciate if you can try out #30890. I posted a link to a prebuilt binary as well

[sayjeyhi]

@howardjohn I tried to test your provided binary file, I used the gcr.io hub and it downloads the image but when starting the container it got probation failure:

Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  10m                   default-scheduler  Successfully assigned istio-system/istiod-56dd66799-24phj to hoory-control-plane
  Normal   Pulling    10m                   kubelet            Pulling image "gcr.io/istio-testing/pilot:1.10-dev"
  Normal   Pulled     8m26s                 kubelet            Successfully pulled image "gcr.io/istio-testing/pilot:1.10-dev" in 1m46.228033006s
  Normal   Created    8m24s                 kubelet            Created container discovery
  Normal   Started    8m24s                 kubelet            Started container discovery
  Warning  Unhealthy  9s (x165 over 8m21s)  kubelet            Readiness probe failed: Get "http://10.244.0.6:8080/ready": dial tcp 10.244.0.6:8080: connect: connection refused

and ingressgateway got this error:

Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  83s (x6 over 6m38s)  default-scheduler  0/1 nodes are available: 1 node(s) didn't match Pod's node affinity.

[howardjohn]

We only support the istioctl client binary. Istio serverside components (istiod/gateway/sidecar) do not support ARM

Closing this since we have completed our support. Thanks for testing!

[sayjeyhi]

@howardjohn thanks, but you mean that we will not be able to use istio ingress getway on M1 locally?

Do you have any suggestions of how we could handle it?!

[howardjohn]

Running Istio on ARM is a ways off, see #21094. Running Istio on ARM+mac is probably even further off unless envoy plans to support this as well.

…

On Wed, Mar 3, 2021 at 12:56 PM Jafar Rezaei ***@***.***> wrote: @howardjohn <https://github.com/howardjohn> thanks, but you mean that we will not be able to use istio ingress getway on M1 locally? Do you have any suggestions of how we could handle it?! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#29596 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEYGXM4V6AZ62BDUGFNCNDTB2O6RANCNFSM4UYKARZA> .

[royathan]

@howardjohn I believe envoy now supports M1 Arm (as of shortly after your last comment) according to envoy/issues/16482).

What work needs to be done to support M1 Arm on the Istio side of things?

[howardjohn]

See #35176. tl;dr hardware + some CI/CD work. I would expect this to be ready ~soon