Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit4bf43a1

Browse files
authored
add explanation to rollout progress (#1372)
* add explanation to rollout progress* wip
1 parent9ecff56 commit4bf43a1

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

‎_docs/deployments/gitops/monitor-applications.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -613,6 +613,17 @@ caption="Rollout completed for deployment"
613613
max-width="50%"
614614
%}
615615

616+
#### Rollout traffic weights
617+
When traffic management is enabled in your rollout strategy, Codefresh displays accurate traffic weights during a progressive rollout. This means that as your new version is gradually promoted, you can observe the exact percentage of traffic directed to the new and stable versions.
618+
619+
> **NOTE**
620+
> Accurate traffic weights are only displayed if traffic management is configured and used in your rollout strategy.
621+
>
622+
> If traffic management is not used, Codefresh reports simplified, static weights:
623+
>
624+
> - 100 - 0 for a progressing rollout
625+
> - 0 - 100 for a healthy finished rollout
626+
616627
#### Manage ongoing rollout
617628
Click the rollout name to visualize its steps. Manually manage the rollout through the controls in the Rollout Player.
618629
Here you can see that two out of four steps have been completed, 25% of the traffic has been routed, and the rollout has been paused for the defined length of time.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp