Skip to content

Commit cb2eec6

Browse files
committed
adding clicktozoom
Signed-off-by: lhajouji <[email protected]>
1 parent 495abc8 commit cb2eec6

File tree

1 file changed

+1
-1
lines changed
  • content/en/blog/_posts/2024-12-17-api-streaming

1 file changed

+1
-1
lines changed

content/en/blog/_posts/2024-12-17-api-streaming/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This can be explained by the differing nature of resource consumption by a singl
1919
This situation poses a genuine risk, potentially overwhelming and crashing any kube-apiserver within seconds due to out-of-memory (OOM) conditions. To better visualize the issue, let's consider the below graph.
2020

2121

22-
{{< figure src="kube-apiserver-memory_usage.png" alt="Monitoring graph showing kube-apiserver memory usage" >}}
22+
{{< figure src="kube-apiserver-memory_usage.png" alt="Monitoring graph showing kube-apiserver memory usage" class="diagram-large" clicktozoom="true" >}}
2323

2424
The graph shows the memory usage of a kube-apiserver during a synthetic test.
2525
(see the [synthetic test](#the-synthetic-test) section for more details).

0 commit comments

Comments
 (0)