Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New guide: protect one service with network policies #111

Merged
merged 7 commits into from
Aug 9, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/_common/install-otterize-cloud-enforcement-off.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
```
2 changes: 1 addition & 1 deletion docs/_common/install-otterize-enforcement-off.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
```


Expand Down
Original file line number Diff line number Diff line change
@@ -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 →" 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 \
Expand Down
Original file line number Diff line number Diff line change
@@ -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>
Expand Down
Original file line number Diff line number Diff line change
@@ -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>
Expand Down
Original file line number Diff line number Diff line change
@@ -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>
Expand Down
4 changes: 2 additions & 2 deletions docs/_common/install-otterize-from-cloud.md
Original file line number Diff line number Diff line change
@@ -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>
Expand Down
2 changes: 1 addition & 1 deletion docs/faq/README.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
sidebar_position: 12
sidebar_position: 13
title: FAQ
---

Expand Down
5 changes: 5 additions & 0 deletions docs/guides/_category_.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"label": "Guides",
"position": 4,
"collapsed": false
}
Loading
Loading