From 343aaf4c927ac6b94b4a3bf1a4d107ab13517eae Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?David=20Wei=C3=9Fe?= Date: Mon, 17 Jun 2024 10:56:38 +0200 Subject: [PATCH] docs: coordinator policy allows logging vars --- docs/docs/troubleshooting.md | 17 ----------------- 1 file changed, 17 deletions(-) diff --git a/docs/docs/troubleshooting.md b/docs/docs/troubleshooting.md index 6ff2b816e..0818d7029 100644 --- a/docs/docs/troubleshooting.md +++ b/docs/docs/troubleshooting.md @@ -50,23 +50,6 @@ spec: # v1.PodSpec # ... ``` -After changing the Coordinator configuration you have to regenerate the policies -for the `coordinator.yml` file. - -```sh -contrast generate coordinator.yml -``` - -:::info - -When updating the Coordinator policy, the policy hash is stored in the -`coordinator-policy.sha256` file. This hash needs to be passed to every -subsequent call to `contrast set` and `contrast verify` using the -`--coordinator-policy-hash` flag, as the hash now differs from the one embedded -into the CLI. - -::: - To access the logs generated by the Coordinator, you can use `kubectl` with the following command.