We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The ProgressiveSync CRD is designed as to support maxTargets and maxParallel as IntOrString.
maxTargets
maxParallel
Consider the following scenario, when you have 4 clusters and a ProgressiveSync similar to
[...] stages: - name: one cluster maxTargets: 1 maxParallel: 1 targets: clusters: selector: name: cluster-one - name: everything else maxTargets: 100% maxParallel: 25% targets: clusters: selector: {}
In the second stage, we would expect maxTargets to be 3, but instead we set it to 4. This is because the scheduler looks at every application matching the label selector - in this case all of them.
3
4
We need to change this logic so when we express maxTargets and maxParallel as %, they are scaled against the remaining clusters.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The ProgressiveSync CRD is designed as to support
maxTargets
andmaxParallel
as IntOrString.Consider the following scenario, when you have 4 clusters and a ProgressiveSync similar to
In the second stage, we would expect maxTargets to be
3
, but instead we set it to4
. This is because the scheduler looks at every application matching the label selector - in this case all of them.We need to change this logic so when we express maxTargets and maxParallel as %, they are scaled against the remaining clusters.
The text was updated successfully, but these errors were encountered: