From 6909e6e657ce776ae0d01c4eecc1e446fa2d83e4 Mon Sep 17 00:00:00 2001 From: Nimrod Gilboa Markevich <59927337+nimrod-up9@users.noreply.github.com> Date: Thu, 11 Nov 2021 16:31:47 +0200 Subject: [PATCH] Add link to exposing mizu wiki page in README (#455) --- README.md | 25 +------------------------ 1 file changed, 1 insertion(+), 24 deletions(-) diff --git a/README.md b/README.md index 878664c05..367cbcfe0 100644 --- a/README.md +++ b/README.md @@ -131,30 +131,7 @@ $ mizu clean # mizu will continue running in cluster until clean is executed Removing mizu resources ``` - - -### To run mizu daemon mode with LoadBalancer kubernetes service -```bash -$ mizu tap "^ca.*" --daemon - Mizu will store up to 200MB of traffic, old traffic will be cleared once the limit is reached. - Tapping pods in namespaces "sock-shop" - Waiting for mizu to be ready... (may take a few minutes) - .. - -$ kubectl expose deployment -n mizu --port 80 --target-port 8899 mizu-api-server --type=LoadBalancer --name=mizu-lb - service/mizu-lb exposed - .. - -$ kubectl get services -n mizu - NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE - mizu-api-server ClusterIP 10.107.200.100 80/TCP 5m5s - mizu-lb LoadBalancer 10.107.200.101 34.77.120.116 80:30141/TCP 76s -``` -Note that `LoadBalancer` services only work on supported clusters (usually cloud providers) and might incur extra costs - -If you changed the `mizu-resources-namespace` value, make sure the `-n mizu` flag of the `kubectl expose` command is changed to the value of `mizu-resources-namespace` - -mizu will now be available both by running `mizu view` or by accessing the `EXTERNAL-IP` of the `mizu-lb` service through your browser. +`mizu view` provides one way to access Mizu. For other options, see [Accessing Mizu Wiki Page](https://github.com/up9inc/mizu/wiki/Accessing-Mizu). ## Configuration