Remove references to SPIRE where no longer relevant (#137)

docs/_common/install-otterize-istio-enabled.md

@@ -8,11 +8,11 @@
    --set intentsOperator.operator.enableNetworkPolicyCreation=false
    ```
 
-:::note This example disable network policy enforcement. 
+:::note This example disables network policy enforcement. 
 
-This chart is a bundle of the Otterize intents operator, Otterize credentials operator, Otterize network mapper, and SPIRE.
+This chart is a bundle of the Otterize intents operator, the Otterize credentials operator, and the Otterize network mapper.
 Initial deployment may take a couple of minutes.
-You can add the `--wait` flag for Helm to wait for deployment to complete and all pods to be Ready, or manually watch for all pods to be `Ready` using `kubectl get pods -n otterize-system -w`.
+You can add the `--wait` flag for Helm to wait for deployment to complete and all pods to be `Ready`, or manually watch for all pods to be `Ready` using `kubectl get pods -n otterize-system -w`.
 
 After all the pods are ready you should see the following (or similar) in your terminal when you run `kubectl get pods -n otterize-system`:
 
@@ -22,7 +22,6 @@ credentials-operator-controller-manager-6c56fcfcfb-vg6m9   2/2    Running   0
 intents-operator-controller-manager-65bb6d4b88-bp9pf       2/2    Running   0     9s
 otterize-network-mapper-779fffd959-twjqd                   1/1    Running   0     9s
 otterize-network-sniffer-65mjt                             1/1    Running   0     9s
-otterize-spire-agent-lcbq2                                 1/1    Running   0     9s
-otterize-spire-server-0                                    2/2    Running   0     9s
 otterize-watcher-b9bf87bcd-276nt                           1/1    Running   0     9s
 ```
+:::

docs/_common/install-otterize-istio-watcher.md

@@ -6,9 +6,9 @@ You'll need [Helm](https://helm.sh/docs/intro/install/) installed on your machin
    helm install otterize otterize/otterize-kubernetes -n otterize-system --create-namespace --set networkMapper.istiowatcher.enable=true
    ```
 
-This chart is a bundle of the Otterize intents operator, Otterize credentials operator, Otterize network mapper with the Istio watcher componenet enabled, and SPIRE.
+This chart is a bundle of the Otterize intents operator, the Otterize credentials operator, and the Otterize network mapper with the Istio watcher component enabled.
 Initial deployment may take a couple of minutes.
-You can add the `--wait` flag for Helm to wait for deployment to complete and all pods to be Ready, or manually watch for all pods to be `Ready` using `kubectl get pods -n otterize-system -w`.
+You can add the `--wait` flag for Helm to wait for deployment to complete and all pods to be `Ready`, or manually watch for all pods to be `Ready` using `kubectl get pods -n otterize-system -w`.
 
 After all the pods are ready you should see the following (or similar) in your terminal when you run `kubectl get pods -n otterize-system`:
 
@@ -19,7 +19,5 @@ intents-operator-controller-manager-65bb6d4b88-bp9pf       2/2    Running   0
 otterize-istio-watcher-5c664987d-2mvw9                     1/1    Running   0     9s
 otterize-network-mapper-779fffd959-twjqd                   1/1    Running   0     9s
 otterize-network-sniffer-65mjt                             1/1    Running   0     9s
-otterize-spire-agent-lcbq2                                 1/1    Running   0     9s
-otterize-spire-server-0                                    2/2    Running   0     9s
 otterize-watcher-b9bf87bcd-276nt                           1/1    Running   0     9s
 ```

docs/quick-tutorials/k8s-istio-authorization-policies.mdx

@@ -32,16 +32,12 @@ Before you start, you'll need a Kubernetes cluster. Having a cluster with a [CNI
 
 You can now install (or reinstall) Otterize in your cluster, and optionally connect to Otterize Cloud. Connecting to Cloud lets you:
 1. See what's happening visually in your browser, through the "access graph";
-2. Avoid using SPIRE (which can be installed with Otterize) for issuing certificates, as Otterize Cloud provides a certificate service.
 
 So either forego browser visualization and:
 
 <details>
 <summary>Install Otterize in your cluster, <b>without</b> Otterize Cloud</summary>
 
-:::note Basic system memory requirements
-Otterize requires about 200 MBs and 200 mCPU for all components (including a SPIRE deployment) to install and run properly on Minikube and EKS clusters.
-
 {@include: ../_common/install-otterize-istio-enabled.md}
 
 </details>

docs/quick-tutorials/k8s-istio-watcher.mdx

@@ -26,7 +26,6 @@ Before you start, you'll need a Kubernetes cluster. Having a cluster with a [CNI
 
 You can now install Otterize in your cluster, and optionally connect to Otterize Cloud. Connecting to Cloud lets you:
 1. See what's happening visually in your browser, through the "access graph";
-2. Avoid using SPIRE (which can be installed with Otterize) for issuing certificates, as Otterize Cloud provides a certificate service.
 
 So either forego browser visualization and:
 

docs/quick-tutorials/k8s-mtls.mdx

@@ -34,10 +34,6 @@ So either forego browser visualization and:
 <details>
 <summary>Install Otterize in your cluster, <b>without</b> Otterize Cloud</summary>
 
-:::note Basic system memory requirements
-Otterize requires about 200 MBs and 200 mCPU for all components (including a SPIRE deployment) to install and run properly on Minikube and EKS clusters.
-:::
-
 {@include: ../_common/install-otterize-mtls.md}
 
 </details>

docs/quick-tutorials/k8s-network-policies.mdx

@@ -38,10 +38,6 @@ So either forego browser visualization and:
 <details>
 <summary>Install Otterize in your cluster, <b>without</b> Otterize Cloud</summary>
 
-:::note Basic system memory requirements
-Otterize requires about 200 MBs and 200 mCPU for all components (including a SPIRE deployment) to install and run properly on Minikube and EKS clusters.
-:::
-
 {@include: ../_common/install-otterize.md}
 
 </details>