Closed huiyichanmian closed 1 year ago
Related upstream issue: https://github.com/kubernetes-sigs/controller-runtime/issues/1809 @camilamacedo86 are you still working on this upstream?
@camilamacedo86 Hey Camila, any updates on this? The issue has been open for quite a while, it would be helpful to know the status of KB/C-R release with updated envtest binaries
@varshaprasad96 did we check if we have the code to build the artefacts in this arch? If yes, we can see how we can trigger the build. If not we need to raise the issue in the respective repo/place.
I'm seeing the same etcd dependency issue with s390x architecture, should I create a separate bug for tracking?
Hi @tdaleibm, from researching this issue, it looks like the path of least resistance is going to be adding --arch=amd64
to your setup-envtest
call in the Makefile
to download the Intel binaries, which Darwin arm64 machines can run.
Beyond that, the most recent Kubebuilder releases and onward now have a prebuilt binary for Darwin, but this looks like its related to a downstream dependency in etcd
, which still does not have Darwin arm64 releases as of nine days ago. I will do some more digging and see what's involved in getting full native Darwin arm64 support.
One other thing you can look at is sideloading a native Darwin arm64 binary if you can download and build etcd
yourself.
Thanks, looks like my issue is just for s390x, since kubebuilder is still not available for this arch https://github.com/kubernetes-sigs/kubebuilder/issues/2298.
@huiyichanmian,
The darwin/arm64 is still not supported by kubebuilder-tools. See that we open a issue for that: https://github.com/kubernetes-sigs/kubebuilder/issues/2664.
c/c @varshaprasad96 @ryantking @rashmigottipati
@camilamacedo86
So it looks like I'll have to build on a linux system.
We are very close to beginning to provide it from Kubebuilder and then be able to add it to SDK as well, See: https://github.com/kubernetes-sigs/kubebuilder/issues/2664#issuecomment-1149956592
We hope to achieve the goal for the next KB release and begin to provide the kubebuilder tools for darwin/arm64 from k8s 1.24
c/c @rashmigottipati @varshaprasad96 @everettraven @ryantking
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
When I use the operator-sdk in the reference document and execute make docker build, the following error occurs:
My working environment:
go version go1.17.8 darwin/arm64
operator-sdk version: "v1.19.0", commit: "728682c347f6335ee2a610e08790a5e1411508f4", kubernetes version: "1.23", go version: "go1.17.8", GOOS: "darwin", GOARCH: "arm64"