add three subdir in rollout doc (#693)

Signed-off-by: LiZhenCheng9527 <[email protected]>

docs/content/en/docs/fleet-manager/rollout/abtest/_index.md

@@ -0,0 +1,18 @@
+---
+title: "A/B Testing"
+linkTitle: "A/B Testing"
+weight: 50
+description: >
+  A comprehensive guide on Kurator's A/B Testing, providing an overview and quick start guide.
+---
+
+## Introduction
+
+A/B Testing is a method of comparing two versions of an application to validate which performs better.
+It essentially involves a controlled experiment where users are randomly allocated into groups at the same time, with each group experiencing a different version of the application.
+The metrics from their usage are then analyzed to select the superior version based on the results. The A/B Testing can also be used to route selective users to the new version, allowing their real-world feedback on the new release to be gathered.
+
+- **Use Case**: There are two application services with identical backend functionality but different frontend UIs. It is now necessary to validate which UI design leads to a better user experience. In this scenario, A/B Testing should be used to deploy both versions of the service in a live environment. The UI that demonstrates superior user metrics and outcomes can then be selected for full release.
+- **Functionality**: Provide configuration of A/B Testing and trigger an A/B Testing on new release.
+
+By allowing users to deploy applications and their A/B Testing configurations in a single place, Kurator streamlines A/B Testing through automated GitOps workflows for unified deployment and validation.

docs/content/en/docs/fleet-manager/rollout/abtest.md → docs/content/en/docs/fleet-manager/rollout/abtest/abtest.md

@@ -1,22 +1,11 @@
 ---
-title: "A/B Testing"
-linkTitle: "A/B Testing"
-weight: 30
+title: "Istio A/B Testing"
+linkTitle: "Istio A/B Testing"
+weight: 20
 description: >
-  A comprehensive guide on Kurator's A/B Testing, providing an overview and quick start guide.
+  A comprehensive guide on Kurator's A/B Testing uses Istio as ingress, providing an overview and quick start guide.
 ---
 
-## Introduction
-
-A/B Testing is a method of comparing two versions of an application to validate which performs better.
-It essentially involves a controlled experiment where users are randomly allocated into groups at the same time, with each group experiencing a different version of the application.
-The metrics from their usage are then analyzed to select the superior version based on the results. The A/B Testing can also be used to route selective users to the new version, allowing their real-world feedback on the new release to be gathered.
-
-- **Use Case**: There are two application services with identical backend functionality but different frontend UIs. It is now necessary to validate which UI design leads to a better user experience. In this scenario, A/B Testing should be used to deploy both versions of the service in a live environment. The UI that demonstrates superior user metrics and outcomes can then be selected for full release.
-- **Functionality**: Provide configuration of A/B Testing and trigger an A/B Testing on new release.
-
-By allowing users to deploy applications and their A/B Testing configurations in a single place, Kurator streamlines A/B Testing through automated GitOps workflows for unified deployment and validation.
-
 ## Prerequisites
 
 In the subsequent sections, we'll guide you through a hands-on demonstration.

docs/content/en/docs/fleet-manager/rollout/blue-green/_index.md

@@ -0,0 +1,18 @@
+---
+title: "Blue/Green Deployment"
+linkTitle: "Blue/Green Deployment"
+weight: 50
+description: >
+  A comprehensive guide on Kurator's Blue/Green Deployment, providing an overview and quick start guide.
+---
+
+## Introduction
+
+In Blue/Green Deployment, there are two separate live production environments - the blue environment and the green environment. The blue environment runs the existing version receiving real-time traffic, while the green environment hosts the new release. At any given time, only one of the environments is live with real traffic.
+
+The key benefit of Blue/Green Deployment is that if issues arise in the new version, traffic can be instantaneously switched back to the blue environment running the old version, avoiding any downtime and resulting losses. This allows seamless rollback to the previous known-good release in the event validation fails.
+
+- **Use Case**: If issues are encountered that prevent the new version from functioning properly, the testing process should immediately switch the traffic back to the previously stable legacy release. This ensures users continue receiving an optimal service experience without interruption while the new release issues are addressed.
+- **Functionality**: Provides configuration of Blue/Green Deployment and triggers a Blue/Green Deploymenton new release.
+
+By allowing users to deploy applications and their Blue/Green Deployment configurations in a single place, Kurator streamlines Blue/Green Deployment through automated GitOps workflows for unified deployment and validation.

docs/content/en/docs/fleet-manager/rollout/blue-green.md → docs/content/en/docs/fleet-manager/rollout/blue-green/blue-green.md

@@ -1,22 +1,11 @@
 ---
-title: "Blue/Green Deployment"
-linkTitle: "Blue/Green Deployment"
-weight: 40
+title: "Istio Blue/Green Deployment"
+linkTitle: "Istio Blue/Green Deployment"
+weight: 20
 description: >
-  A comprehensive guide on Kurator's Blue/Green Deployment, providing an overview and quick start guide.
+  A comprehensive guide on Kurator's Blue/Green Deployment uses Istio as ingress, providing an overview and quick start guide.
 ---
 
-## Introduction
-
-In Blue/Green Deployment, there are two separate live production environments - the blue environment and the green environment. The blue environment runs the existing version receiving real-time traffic, while the green environment hosts the new release. At any given time, only one of the environments is live with real traffic.
-
-The key benefit of Blue/Green Deployment is that if issues arise in the new version, traffic can be instantaneously switched back to the blue environment running the old version, avoiding any downtime and resulting losses. This allows seamless rollback to the previous known-good release in the event validation fails.
-
-- **Use Case**: If issues are encountered that prevent the new version from functioning properly, the testing process should immediately switch the traffic back to the previously stable legacy release. This ensures users continue receiving an optimal service experience without interruption while the new release issues are addressed.
-- **Functionality**: Provides configuration of Blue/Green Deployment and triggers a Blue/Green Deploymenton new release.
-
-By allowing users to deploy applications and their Blue/Green Deployment configurations in a single place, Kurator streamlines Blue/Green Deployment through automated GitOps workflows for unified deployment and validation.
-
 ## Prerequisites
 
 In the subsequent sections, we'll guide you through a hands-on demonstration.

docs/content/en/docs/fleet-manager/rollout/canary/_index.md

@@ -0,0 +1,18 @@
+---
+title: "Canary Deployment"
+linkTitle: "Canary Deployment"
+weight: 50
+description: >
+  A comprehensive guide on Kurator's Canary Deployment, providing an overview and quick start guide.
+---
+
+## Introduction
+
+Canary Deployment is a software release strategy.
+It refers to releasing a new software version to only a very small percentage of users first for testing, to observe if there are any issues. Based on the test results, determine whether to gradually roll out the release to more users.
+It aims to maximize reducing the impact on users after a new version goes live. It is considered a safer and more reliable method of software updates.
+
+- **Use Case**: When the system undergoes API changes that require validation through real-world usage, a Canary Deployment should be leveraged to gradually roll out and validate the changes. This incremental approach helps ensure any potential issues are identified and addressed before being exposed to all services/traffic.
+- **Functionality**: Provides configuration of Canary Deployment and triggers a Canary Deployment on new release.
+
+By allowing users to deploy applications and their canary configurations in a single place, Kurator streamlines Canary Deployment through automated GitOps workflows for unified deployment and validation.

docs/content/en/docs/fleet-manager/rollout/canary.md → docs/content/en/docs/fleet-manager/rollout/canary/canary.md

@@ -1,22 +1,11 @@
 ---
-title: "Canary Deployment"
-linkTitle: "Canary Deployment"
+title: "Istio Canary Deployment"
+linkTitle: "Istio Canary Deployment"
 weight: 20
 description: >
-  A comprehensive guide on Kurator's Canary Deployment, providing an overview and quick start guide.
+  A comprehensive guide on Kurator's Canary Deployment uses Istio as ingress, providing an overview and quick start guide.
 ---
 
-## Introduction
-
-Canary Deployment is a software release strategy.
-It refers to releasing a new software version to only a very small percentage of users first for testing, to observe if there are any issues. Based on the test results, determine whether to gradually roll out the release to more users.
-It aims to maximize reducing the impact on users after a new version goes live. It is considered a safer and more reliable method of software updates.
-
-- **Use Case**: When the system undergoes API changes that require validation through real-world usage, a Canary Deployment should be leveraged to gradually roll out and validate the changes. This incremental approach helps ensure any potential issues are identified and addressed before being exposed to all services/traffic.
-- **Functionality**: Provides configuration of Canary Deployment and triggers a Canary Deployment on new release.
-
-By allowing users to deploy applications and their canary configurations in a single place, Kurator streamlines Canary Deployment through automated GitOps workflows for unified deployment and validation.
-
 ## prerequisites
 
 In the subsequent sections, we'll guide you through a hands-on demonstration.