diff --git a/libs/domains/services/feature/src/lib/keda/components/keda-settings.tsx b/libs/domains/services/feature/src/lib/keda/components/keda-settings.tsx
index e26289d60d7..b0d169cc99f 100644
--- a/libs/domains/services/feature/src/lib/keda/components/keda-settings.tsx
+++ b/libs/domains/services/feature/src/lib/keda/components/keda-settings.tsx
@@ -35,18 +35,6 @@ export function KedaSettings({
requireMinLessThanMax={true}
/>
-
- For applications requiring high availability, set Minimum Instances to at least 2 to maintain service
- availability during pod failures or cluster maintenance.
-
- Always assume one instance may fail due to node maintenance or issues. -
-- To ensure high availability, set Minimum Instances to 2 if your app can run on 1 instance. -
-- If your application requires more than one instance to handle necessary traffic, set the minimum to 3 or higher to guarantee redundancy during a single failure. -
-Always assume one instance may fail due to node maintenance or issues.
-To ensure high availability, set Minimum Instances to 2 if your app can run on 1 instance.
-- If your application requires more than one instance to handle necessary traffic, set the minimum to 3 or - higher to guarantee redundancy during a single failure. -
- {isProduction && hasSingleInstance && ( + {isProduction && hasSingleInstance && ( +Always assume one instance may fail due to node maintenance or issues.
+To ensure high availability, set Minimum Instances to 2 if your app can run on 1 instance.
++ If your application requires more than one instance to handle necessary traffic, set the minimum to 3 or + higher to guarantee redundancy during a single failure. +
We strongly discourage running your production environment with only one instance. This setup might create service downtime in case of cluster upgrades.
- )} -