From 8c3f2d7aa9d6a2ab2c0ce13334353700b4586f3b Mon Sep 17 00:00:00 2001 From: Jakub Scholz Date: Fri, 9 Mar 2018 11:04:40 +0100 Subject: [PATCH] Fix typo Minikube versus Minishift --- .../adoc/appendix_deploying_kubernetes_openshift_cluster.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/adoc/appendix_deploying_kubernetes_openshift_cluster.adoc b/documentation/adoc/appendix_deploying_kubernetes_openshift_cluster.adoc index 5cef67772c..dbf4b3eed5 100644 --- a/documentation/adoc/appendix_deploying_kubernetes_openshift_cluster.adoc +++ b/documentation/adoc/appendix_deploying_kubernetes_openshift_cluster.adoc @@ -34,7 +34,7 @@ https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md[here]. Another option is to use `Minishift`. `MiniShift` is an OpenShift installation within a VM. It can be downloaded and installed from the https://docs.openshift.org/latest/minishift/index.html[Minishift website]. Depending on the number of brokers -you want to deploy inside the cluster and if you need Kafka Connect running as well, it could be worth running `Minikube` +you want to deploy inside the cluster and if you need Kafka Connect running as well, it could be worth running `Minishift` at least with 4 GB of RAM instead of the default 2 GB. Once installed, `Minishift` can be started using the following command: