You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not possible to spread pod over different defined zones with topologySpreadConstraints at the moment.
What is the value to the end user? (why is it a priority?)
Possibility to spread Pods over Zones or other topology labels.
How will we know we have a good solution? (acceptance criteria)
PR already created with a solution and follows the standard kubernetes approche in regrads of topologySpreadConstraints.
Additional context
PR already created with a solution.
The text was updated successfully, but these errors were encountered:
@JohnStrunk Is it possible to release a new version. Without we can't use the new features.
helm search repo backube/snapscheduler
NAME CHART VERSION APP VERSION DESCRIPTION
backube/snapscheduler 3.0.0 3.0.0 An operator to take scheduled snapshots of Kube...
Describe the feature you'd like to have.
It's not possible to spread pod over different defined zones with topologySpreadConstraints at the moment.
What is the value to the end user? (why is it a priority?)
Possibility to spread Pods over Zones or other topology labels.
How will we know we have a good solution? (acceptance criteria)
PR already created with a solution and follows the standard kubernetes approche in regrads of topologySpreadConstraints.
Additional context
PR already created with a solution.
The text was updated successfully, but these errors were encountered: