fix(Pixie):Add Advanced Configuration section

Signed-off-by: Hannah Troisi <htroisi@pixielabs.ai>
newrelic · Jun 13, 2022 · 85b946d · 85b946d
1 parent 8dc102b
commit 85b946d
Show file tree

Hide file tree

Showing 6 changed files with 12 additions and 11 deletions.
diff --git a/...uto-telemetry-pixie/manage-pixie-data.mdx → ...anced-configuration/manage-pixie-data.mdx b/...uto-telemetry-pixie/manage-pixie-data.mdx → ...anced-configuration/manage-pixie-data.mdx
diff --git a/...o-telemetry-pixie/manage-pixie-memory.mdx → ...ced-configuration/manage-pixie-memory.mdx b/...o-telemetry-pixie/manage-pixie-memory.mdx → ...ced-configuration/manage-pixie-memory.mdx
diff --git a/...bernetes-pixie/auto-telemetry-pixie/troubleshooting/high-memory-consumption.mdx b/...bernetes-pixie/auto-telemetry-pixie/troubleshooting/high-memory-consumption.mdx
@@ -1,5 +1,5 @@
 ---
-title: High memory consumption for the Pixie integration 
+title: High memory consumption for the Pixie integration
 tags:
   - Integrations
   - New Relic Pixie integration
@@ -15,4 +15,4 @@ You have completed the [installation procedure](/docs/kubernetes-pixie/auto-tele
 
 ## Solution
 
-Pixie [uses memory for two different purposes](/docs/kubernetes-pixie/auto-telemetry-pixie/manage-pixie-memory#memory-usage): collecting telemetry data and short-term in-cluster storage of this data. If you’d like to specify a different amount of memory for short-term storage, you can [configure the short-term storage memory limit](/docs/kubernetes-pixie/auto-telemetry-pixie/manage-pixie-memory#reduce-data-storage) during installation.
+Pixie [uses memory for two different purposes](/docs/kubernetes-pixie/auto-telemetry-pixie/advanced-configuration/manage-pixie-memory#memory-usage): collecting telemetry data and short-term in-cluster storage of this data. If you’d like to specify a different amount of memory for short-term storage, you can [configure the short-term storage memory limit](/docs/kubernetes-pixie/auto-telemetry-pixie/advanced-configuration/manage-pixie-memory#reduce-data-storage) during installation.
diff --git a/...rnetes-pixie/auto-telemetry-pixie/troubleshooting/pods-frequently-oomkilled.mdx b/...rnetes-pixie/auto-telemetry-pixie/troubleshooting/pods-frequently-oomkilled.mdx
@@ -17,4 +17,4 @@ You have completed the [installation procedure](/docs/kubernetes-pixie/auto-tele
 
 Part of the benefit of deploying on Kubernetes is that Kubernetes will OOMKill pods that are using too many resources to protect the other pods in the cluster.
 
-When Pixie's `vizier-pem` pods exceed the memory limit, they are OOMKilled. Kubernetes does this to protect the other applications, so it won't cause problems on other pods. For `vizier-pem` pods that are regularly being OOMKilled, try [deploying Pixie with more memory](/docs/kubernetes-pixie/auto-telemetry-pixie/manage-pixie-memory#set-memory-limit).
+When Pixie's `vizier-pem` pods exceed the memory limit, they are OOMKilled. Kubernetes does this to protect the other applications, so it won't cause problems on other pods. For `vizier-pem` pods that are regularly being OOMKilled, try [deploying Pixie with more memory](/docs/kubernetes-pixie/auto-telemetry-pixie/advanced-configuration/manage-pixie-memory#set-memory-limit).
diff --git a/...cs/kubernetes-pixie/auto-telemetry-pixie/troubleshooting/pods-stuck-pending.mdx b/...cs/kubernetes-pixie/auto-telemetry-pixie/troubleshooting/pods-stuck-pending.mdx
@@ -18,4 +18,4 @@ You have completed the [installation procedure](/docs/kubernetes-pixie/auto-tele
 
 When the `vizier-pem` pods fail to schedule, this is usually because there are nodes that don't have the requested amount of memory.
 
-Try [reducing the memory request](/docs/kubernetes-pixie/auto-telemetry-pixie/manage-pixie-memory#set-memory-request) down as far as `1Gi`. For particularly large or high traffic clusters, `1Gi` may not be enough and some `vizier-pem` OOMKills might occur. For these clusters, you can set a higher limit than request, such as `2Gi` for the limit.
+Try [reducing the memory request](/docs/kubernetes-pixie/auto-telemetry-pixie/advanced-configuration/manage-pixie-memory#set-memory-request) down as far as `1Gi`. For particularly large or high traffic clusters, `1Gi` may not be enough and some `vizier-pem` OOMKills might occur. For these clusters, you can set a higher limit than request, such as `2Gi` for the limit.
diff --git a/src/nav/kubernetes-pixie.yml b/src/nav/kubernetes-pixie.yml
@@ -89,12 +89,12 @@ pages:
             path: /docs/kubernetes-pixie/auto-telemetry-pixie/understand-use-data/dashboard-pixie-data
           - title: Query Pixie data
             path: /docs/kubernetes-pixie/auto-telemetry-pixie/understand-use-data/query-pixie-data
-      - title: Manage Pixie data
-        path: /docs/kubernetes-pixie/auto-telemetry-pixie/manage-pixie-data
-      - title: Manage Pixie memory
-        path: /docs/kubernetes-pixie/auto-telemetry-pixie/manage-pixie-memory
-      - title: Data and security for Auto-telemetry with Pixie
-        path: /docs/kubernetes-pixie/auto-telemetry-pixie/pixie-data-security-overview
+      - title: Advanced configuration
+        pages:
+          - title: Manage Pixie data
+            path: /docs/kubernetes-pixie/auto-telemetry-pixie/advanced-configuration/manage-pixie-data
+          - title: Manage Pixie memory
+            path: /docs/kubernetes-pixie/auto-telemetry-pixie/advanced-configuration/manage-pixie-memory
       - title: Troubleshooting
         pages:
           - title: Pods stuck in pending state
@@ -105,4 +105,5 @@ pages:
             path: /docs/kubernetes-pixie/auto-telemetry-pixie/troubleshooting/high-memory-consumption
           - title: Get Pixie logs
             path: /docs/kubernetes-pixie/auto-telemetry-pixie/troubleshooting/get-pixie-logs
-
+      - title: Data and security for Auto-telemetry with Pixie
+        path: /docs/kubernetes-pixie/auto-telemetry-pixie/pixie-data-security-overview