Use Kubeadm instead of Minikube to Support Local Power Build #1477
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
triage/unresolved
Indicates an issue that can not or will not be resolved.
Type of question
Are you asking about community best practices, how to implement a specific feature, or about general context and help around the operator-sdk?
How to implement a specific feature
Question
What did you do?
I am working to add IBM Power (PPC64LE) support for OLM.
I have run into a few issues with the local setup including that Minikube support for Power is limited (almost nonexistent at this time).
I would like to either change the run-local Make target to use kubeadm for all local runs or conditionally choose kubeadm if the architecture is Power.
I would like advice on what would be more acceptable:
Currently, I have modified the scripts/build_local.sh file to use kubeadm. This allows me to build OLM locally on Power.
Environment
2dea823
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean", BuildDate:"2020-03-12T21:03:42Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/ppc64le"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5", GitCommit:"e0fccafd69541e3750d460ba0f9743b90336f24f", GitTreeState:"clean", BuildDate:"2020-04-16T11:35:47Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/ppc64le"}
Local: single node cluster
Additional context
We are wanting to use OLM on Power, so we need to be able to build it on the architecture.
The text was updated successfully, but these errors were encountered: