Skip to content

Commit b64286e

Browse files
authored
removed duplicated paragraph (#1503)
duplicate paragraph fixed in production guidance section
1 parent ea0d2b5 commit b64286e

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

deploy-manage/production-guidance/scaling-considerations.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@ applies_to:
1212

1313
Knowing when and how to scale your deployment is critical, especially when unexpected workloads hit. Adding more nodes or adjusting resources is not always the best solution. Instead, scaling should be based on real workload patterns and informed decision-making.
1414

15-
In orchestrated or managed deployments, [Autoscaling](/deploy-manage/autoscaling.md) can automatically adjust cluster resources based on demand, reducing operational overhead. However, in self-managed environments, scaling is a manual process, requiring careful planning to adapt to workload changes and ensure the cluster remains performant and resilient.
16-
1715
In orchestrated or managed deployments, [Autoscaling](/deploy-manage/autoscaling.md) can automatically adjust cluster resources based on demand, reducing operational overhead. However, if you choose not to use it, or in self-managed environments, scaling becomes a manual process that requires careful planning to adapt to workload changes and ensure the cluster remains performant and resilient.
1816

1917
::::{note}

0 commit comments

Comments
 (0)