Getting a Arm64 CI for kubernetes

[lub...@gmail.com]

I have created an issue for Arm64 CI, can anyone help to check it?

For now, I don't know how to add Arm64 servers into the k8s CI system.

Thanks.

[Davanum Srinivas]

@lubinsz,

The backbone of all the CI jobs currently is either 

1) kube-up.sh ( https://github.com/kubernetes/kubernetes/tree/master/cluster )

2) kind ( https://github.com/kubernetes/kubernetes/tree/master/cluster )

Does either of them work out of the box with arm64? That would be step 1.

You can also run a prow job locally using:

https://github.com/kubernetes/test-infra/blob/master/prow/build_test_update.md#using-pj-on-kindsh

So there's a bunch of work we need to do before we can get there.

Also given the current challenges with the CI jobs, everyone is fully occupied :( So its going to be tough from a practical point of view to spend time on this right now unless we get more hands/eyes to help with CI stuff.

Thanks,

Dims

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-testing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-te...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-testing/7efafa21-7e8d-449f-aadd-cc2ef97f0879%40googlegroups.com.

--

Davanum Srinivas :: https://twitter.com/dims

[Benjamin Elder]

Right now I'd really like to see more progress in wg-k8s-infra helping us get infra under the CNCF where anyone can join the efforts to manage it.

Until then, I'd not be super keen on burning my own cycles to add more infra.

We have an existing system to publish third party results to CI which we've provided access to for arm results already, and so far those results are generally stale / unstable ...

https://testgrid.k8s.io/conformance-arm
https://testgrid.k8s.io/conformance-kind#kind,%20v1.14%20(dev,%20ARM64)

To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-testing/CANw6fcGN1TwhfORD6%2BB75bCGAQMyHvnmOzaj6MaEsbde_pCJpg%40mail.gmail.com.