Skip to content

Commit

Permalink
docs: replace Kind with Minikube for simple test installations
Browse files Browse the repository at this point in the history
- Updated installation instructions to use Minikube instead of Kind.
- Modified references throughout relevant pages to reflect Minikube.
- Ensured steps are clear for users to set up Minikube.

Closes kumahq#1649

Signed-off-by: dascole [email protected]
Signed-off-by: Joe Dascole <[email protected]>
  • Loading branch information
pikturemerollin authored and lahabana committed Oct 18, 2024
1 parent cb37388 commit 55d2b7b
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 8 deletions.
16 changes: 12 additions & 4 deletions app/_src/guides/federate.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,11 +24,19 @@ It can be a cluster running locally or in a public cloud like AWS EKS, GCP GKE,
{% endtip %}

```sh
kind create cluster --name=mesh-global
minikube start -p kuma-mesh-global
```

By default, Kind does not support LoadBalancer therefore we need to configure it by following this [guide](https://kind.sigs.k8s.io/docs/user/loadbalancer/).
Note that all public cloud providers support load balancers out of the box.
### Setup the minikube tunnel
If you are using Minikube for local testing, you can take advantage of the built-in minikube tunnel command. This command allows load balancer addresses to be provisioned using localhost.

{% tip %}
Using nohup will allow the tunnel to continue running should your current terminal session end.
{% endtip %}

```sh
nohup minikube tunnel -p &
```

### Deploy a global control plane

Expand Down Expand Up @@ -151,4 +159,4 @@ NAMESPACE NAME TARGETREF KIND

## Next steps

* Read the [multi-zone](/docs/{{ page.version }}/production/cp-deployment/multi-zone) docs to learn more about this deployment model and cross-zone connectivity.
* Read the [multi-zone](/docs/{{ page.version }}/production/cp-deployment/multi-zone) docs to learn more about this deployment model and cross-zone connectivity.
8 changes: 4 additions & 4 deletions app/_src/quickstart/kubernetes-demo.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,14 +21,14 @@ demo-app --> redis

## Prerequisites
- [Helm](https://helm.sh/) - a package manager for Kubernetes
- [Kind](https://kind.sigs.k8s.io/) - a tool for running local Kubernetes clusters
- [Minikube](https://minikube.sigs.k8s.io/docs/) - a tool for running local Kubernetes clusters

## Start Kubernetes cluster

Start a new Kubernetes cluster on your local machine by executing:
Start a new Kubernetes cluster on your local machine by executing the command below. The -p option creates a new profile named 'kuma-zone'."

```sh
kind create cluster --name=mesh-zone
minikube start -p kuma-zone
```

{% tip %}
Expand Down Expand Up @@ -195,4 +195,4 @@ However, the traffic to `redis` from any other service than `demo-app` is not al
* [Federate](/docs/{{ page.version }}/guides/federate) zone into a multizone deployment.
* Learn more about what you can do with the [GUI](/docs/{{ page.version }}/production/gui).
* Read the [full documentation](/docs/{{ page.version }}/) to learn about all the capabilities of {{site.mesh_product_name}}.
{% if site.mesh_product_name == "Kuma" %}* Chat with us at the official [Kuma Slack](/community) for questions or feedback.{% endif %}
{% if site.mesh_product_name == "Kuma" %}* Chat with us at the official [Kuma Slack](/community) for questions or feedback.{% endif %}

0 comments on commit 55d2b7b

Please sign in to comment.