TRA-3903 more docs (#438)

* Update README.md and PERMISSIONS.md

* Update PERMISSIONS.md

* Update README.md

* Update PERMISSIONS.md

* Update PERMISSIONS.md
This commit is contained in:
RamiBerm 2021-11-07 12:23:15 +02:00 committed by GitHub
parent 6811bd5050
commit a866576cfc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 2 deletions

View File

@ -184,6 +184,8 @@ and when changed it will support accessing by IP
Mizu can be ran detached from the cli using the daemon flag: `mizu tap --daemon`. This type of mizu instance will run indefinitely in the cluster. Mizu can be ran detached from the cli using the daemon flag: `mizu tap --daemon`. This type of mizu instance will run indefinitely in the cluster.
Please note that daemon mode requires you to have RBAC creation permissions, see the [permissions](docs/PERMISSIONS.md) doc for more details.
In order to access a daemon mizu you will have to run `mizu view` after running the `tap --daemon` command. In order to access a daemon mizu you will have to run `mizu view` after running the `tap --daemon` command.
To stop the detached mizu instance and clean all cluster side resources, run `mizu clean` To stop the detached mizu instance and clean all cluster side resources, run `mizu clean`

View File

@ -57,9 +57,11 @@ Mizu needs following permissions on your Kubernetes cluster to run properly
- get - get
``` ```
## Permissions required for service / pod name resolving (opt) ## Permissions required running with --daemon flag or (optional) for service / pod name resolving
Optionally, for proper resolving of IP addresses to Kubernetes service name, Mizu needs below permissions: Mandatory permissions for running with `--daemon` flag.
Optional for service/pod name resolving in non daemon mode
```yaml ```yaml
- apiGroups: - apiGroups: