New guide: protect one service with network policies (#111)

Co-authored-by: Ori Shoshan <[email protected]>
otterize · Aug 9, 2023 · d5e6011 · d5e6011
1 parent d1c2b52
commit d5e6011
Show file tree

Hide file tree

Showing 33 changed files with 447 additions and 51 deletions.
diff --git a/docs/_common/install-otterize-cloud-enforcement-off.md b/docs/_common/install-otterize-cloud-enforcement-off.md
@@ -4,6 +4,6 @@ helm upgrade --install otterize otterize/otterize-kubernetes \
 -n otterize-system --create-namespace \
 --set global.otterizeCloud.credentials.clientId=client_id \
 --set global.otterizeCloud.credentials.clientSecret=client_secret \
---set intentsOperator.operator.enableEnforcement=false \
+--set intentsOperator.operator.mode=defaultShadow \
 --set credentialsOperator.useOtterizeCloud=true
 ```
diff --git a/docs/_common/install-otterize-enforcement-off.md b/docs/_common/install-otterize-enforcement-off.md
@@ -2,7 +2,7 @@
    helm repo add otterize https://helm.otterize.com
    helm repo update
    helm install otterize otterize/otterize-kubernetes -n otterize-system --create-namespace \
-   --set intentsOperator.operator.enableEnforcement=false
+   --set intentsOperator.operator.mode=defaultShadow
    ```
 
 

diff --git a/...on/install-otterize-from-cloud-with-enforcement-and-kafka-watcher-no-netpols.md b/...on/install-otterize-from-cloud-with-enforcement-and-kafka-watcher-no-netpols.md
@@ -1,7 +1,7 @@
 If no Kubernetes clusters are connected to your account, click the "connect your cluster" button to:
 1. Create a Cloud cluster object, specifying its name and the name of an environment to which all namespaces in that cluster will belong, by default.
 2. Connect it with your actual Kubernetes cluster, by clicking on the "Connection guide &rarr;" link and running the Helm commands shown there.
-    1. Follow the instructions to install Otterize <b>with enforcement on</b> (not in shadow mode) for this tutorial. In other words, <b>omit</b> the following flag in the Helm command: `--set intentsOperator.operator.enableEnforcement=false` 
+    1. Follow the instructions to install Otterize <b>with enforcement on</b> (not in shadow mode) for this tutorial. In other words, <b>omit</b> the following flag in the Helm command: `--set intentsOperator.operator.mode=defaultShadow` 
     2. And <b>add</b> the following flags to the Helm command: 
        ```
        --set intentsOperator.operator.enableNetworkPolicyCreation=false \ 

diff --git a/docs/_common/install-otterize-from-cloud-with-enforcement-with-istiowatcher.md b/docs/_common/install-otterize-from-cloud-with-enforcement-with-istiowatcher.md
@@ -1,7 +1,7 @@
 If no Kubernetes clusters are connected to your account, click the "connect your cluster" button to:
 1. Create a Cloud cluster object, specifying its name and the name of an environment to which all namespaces in that cluster will belong, by default.
 2. Connect it with your actual Kubernetes cluster, by clicking on the "Connection guide &rarr;" link and running the Helm commands shown there.
-    1. Follow the instructions to install Otterize <b>with enforcement on</b> (not in shadow mode) for this tutorial. In other words, <b>omit</b> the following flag in the Helm command: `--set intentsOperator.operator.enableEnforcement=false`
+    1. Follow the instructions to install Otterize <b>with enforcement on</b> (not in shadow mode) for this tutorial. In other words, <b>omit</b> the following flag in the Helm command: `--set intentsOperator.operator.mode=defaultShadow`
     2. And <b>add</b> the following flag to the Helm command:  `--set networkMapper.istiowatcher.enable=true`
 
 <details>

diff --git a/docs/_common/install-otterize-from-cloud-with-enforcement.md b/docs/_common/install-otterize-from-cloud-with-enforcement.md
@@ -1,7 +1,7 @@
 If no Kubernetes clusters are connected to your account, click the "connect your cluster" button to:
 1. Create a Cloud cluster object, specifying its name and the name of an environment to which all namespaces in that cluster will belong, by default.
 2. Connect it with your actual Kubernetes cluster, by clicking on the "Connection guide &rarr;" link and running the Helm commands shown there.
-    1. Follow the instructions to install Otterize <b>with enforcement on</b> (not in shadow mode) for this tutorial. In other words, <b>omit</b> the following flag in the Helm command: `--set intentsOperator.operator.enableEnforcement=false`
+    1. Follow the instructions to install Otterize <b>with enforcement on</b> (not in shadow mode) for this tutorial. In other words, <b>omit</b> the following flag in the Helm command: `--set intentsOperator.operator.mode=defaultShadow`
 
 <details>
 <summary>More details, if you're curious</summary>

diff --git a/docs/_common/install-otterize-from-cloud-with-istio-enforcement.md b/docs/_common/install-otterize-from-cloud-with-istio-enforcement.md
@@ -1,7 +1,7 @@
 If no Kubernetes clusters are connected to your account, click the "connect your cluster" button to:
 1. Create a Cloud cluster object, specifying its name and the name of an environment to which all namespaces in that cluster will belong, by default.
 2. Connect it with your actual Kubernetes cluster, by clicking on the "Connection guide &rarr;" link and running the Helm commands shown there.
-    1. Follow the instructions to install Otterize <b>with enforcement on</b> (not in shadow mode) for this tutorial. In other words, <b>omit</b> the following flag in the Helm command: `--set intentsOperator.operator.enableEnforcement=false`
+    1. Follow the instructions to install Otterize <b>with enforcement on</b> (not in shadow mode) for this tutorial. In other words, <b>omit</b> the following flag in the Helm command: `--set intentsOperator.operator.mode=defaultShadow`
 
 <details>
 <summary>More details, if you're curious</summary>

diff --git a/docs/_common/install-otterize-from-cloud.md b/docs/_common/install-otterize-from-cloud.md
@@ -1,6 +1,6 @@
-If no Kubernetes clusters are connected to your account, click the "connect your cluster" button to:
+If no Kubernetes clusters are connected to your account, click the "Connect your cluster" button to:
 1. Create a Cloud cluster object, specifying its name and the name of an environment to which all namespaces in that cluster will belong, by default.
-2. Connect it with your actual Kubernetes cluster, by clicking on the "Connection guide &rarr;" link and running the Helm commands shown there. You'll want to keep enforcement off, and be in shadow mode.
+2. Connect it with your actual Kubernetes cluster, by clicking on the "Connection guide &rarr;" link and running the Helm commands shown there. You'll want to use `mode=defaultShadow` so you're in shadow mode on every server until you're ready to protect it.
 
 <details>
 <summary>More details, if you're curious</summary>

diff --git a/docs/faq/README.mdx b/docs/faq/README.mdx
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 12
+sidebar_position: 13
 title: FAQ
 ---
 

diff --git a/docs/guides/_category_.json b/docs/guides/_category_.json
@@ -0,0 +1,5 @@
+{
+  "label": "Guides",
+  "position": 4,
+  "collapsed": false
+}