-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
unable to find a version that was supported for platform darwin/arm64 #1657
Comments
It looks like there is no kubebuilder-tools that support However, there is a workaround for M1 Mac. Just modify Makefile's test: manifests generate fmt vet envtest ## Run tests.
- KUBEBUILDER_ASSETS="$(shell $(ENVTEST) use $(ENVTEST_K8S_VERSION) -p path)" go test ./... -coverprofile cover.out
+ KUBEBUILDER_ASSETS="$(shell $(ENVTEST) --arch=amd64 use $(ENVTEST_K8S_VERSION) -p path)" go test ./... -coverprofile cover.out |
Native binaries for darwin/arm64 would be much appreciated! |
pushed a PR to init the mitigation of this, you can give a thumb up in here --> kubernetes-sigs/kubebuilder#2516 |
when do you plan to release a new version which includes this fix? |
envtest needs this switch to allow you to run from m1 macbooks. This is noted in a helpful comment here: kubernetes-sigs/controller-runtime#1657 (comment)
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale The latest progress is here: kubernetes-sigs/kubebuilder#1932 (comment) |
kubebuilder-tools does not yet support darwin/arm64. Providing the "--arch amd64" is a workaround for running the setup-envtest on M1 See kubernetes-sigs/controller-runtime#1657 [#182466806]
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
You can check all available artefacts by looking at: https://storage.googleapis.com/kubebuilder-tools Also, if you want to build a project using this environment with Kubebuilder you need to use go/v4-alpha by initing the project with kubebuilder init --plugins=go/v4-alpha OR you must update/customize your scaffold to use kustomize 4.x version instead. Closing this one as sorted out. |
Went through the OperatorSDK tutorial twice. Once with the traditional/default v3 and once with --plugins="go/v4-alpha" as suggested in kubernetes-sigs/controller-runtime#1657 (comment) . Did a recursive diff between the two directories, and these were the differences. Signed-off-by: Joel Diaz <[email protected]>
Went through the OperatorSDK tutorial twice. Once with the traditional/default v3 and once with --plugins="go/v4-alpha" as suggested in kubernetes-sigs/controller-runtime#1657 (comment) . Did a recursive diff between the two directories, and these were the differences. Signed-off-by: Joel Diaz <[email protected]>
Is controller-runtime tools unsupported on darwin/arm64?
The text was updated successfully, but these errors were encountered: