Skip to content

Commit e4db199

Browse files
authored
Add alternative to OS image (#498)
image builder is good but we may tip folks to use other potential easier way (learning curve perspective) to build an image.
1 parent 5652f88 commit e4db199

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/getting-started.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,9 @@
99
- If you want to use VM, install [Minikube](https://kubernetes.io/docs/tasks/tools/install-minikube/), version 0.30.0 or greater. Also install a [driver](https://github.com/kubernetes/minikube/blob/master/docs/drivers.md). For Linux, we recommend `kvm2`. For MacOS, we recommend `VirtualBox`.
1010
- If you want to use a container, install [Kind](https://github.com/kubernetes-sigs/kind#installation-and-usage).
1111
- If you want to use an existing Kubernetes cluster, prepare a kubeconfig which for this cluster.
12-
1. The CAPO provider requires an OS image (available in OpenStack), which is build like the ones in [image-builder](https://github.com/kubernetes-sigs/image-builder/tree/master/images/capi)
12+
1. The CAPO provider requires an OS image (available in OpenStack), you have several ways to provide one:
13+
- Build image via [image-builder](https://github.com/kubernetes-sigs/image-builder/tree/master/images/capi)
14+
- Or as a test env, you can deploy a VM through OpenStack, log on to the VM and follow the steps in [install kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/) to install container runtime and download kubectl, kubelet and kubeadm but *don't* execute kubeadm, then capture the image in OpenStack cloud and use it as OS image.
1315

1416
## Cluster Creation
1517

0 commit comments

Comments
 (0)