tetragon: for now drop benchmark section

I don't think we need Benchmark section for next release and I think we should spend some time on how to do repeatable benchmarks vs simply push this into the pages. So delete section now and stay tuned for a better implementation. Signed-off-by: John Fastabend <[email protected]>
cilium · Oct 26, 2023 · 0158283 · 0158283
1 parent 7c0c0d4
commit 0158283
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 11 deletions.
diff --git a/docs/content/en/docs/benchmarks/_index.md b/docs/content/en/docs/benchmarks/_index.md
diff --git a/docs/content/en/docs/getting-started/enforcement.md b/docs/content/en/docs/getting-started/enforcement.md
@@ -193,5 +193,4 @@ using policies. Some useful links:
 
 To explore details of writing and implementing policies the [Concepts]({{< ref "/docs/concepts" >}}) is a good jumping off point.
 For installation into production environments we recommend reviewing [Advanced Installations]({{< ref "docs/installation" >}}).
-For a more in depth discussion on Tetragon overhead and how we measure system load try [Benchmarks]({{< ref "docs/benchmarks" >}}).
 Finally [Use Cases]({{< ref "docs/use-cases" >}}) and [Tutorials]({{< ref "docs/tutorials" >}}) cover different uses and deployment concerns related to Tetragon.