Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Provide a spread property on workloads to allow for easy anit-affinity #890

Closed
iliapolo opened this issue Jun 29, 2022 Discussed in #822 · 0 comments · Fixed by #1176
Closed

Provide a spread property on workloads to allow for easy anit-affinity #890

iliapolo opened this issue Jun 29, 2022 Discussed in #822 · 0 comments · Fixed by #1176
Assignees
@vinayak-kukreja
Labels
effort/small 1 day tops feature-request New/Enhanced functionality wanted priority/p1 Should be on near term plans

Comments

@iliapolo
Copy link
Member

Discussed in #822

Originally posted by iliapolo June 9, 2022
It's good practice to enforce that multiple pods of the same workload don't end up on the same host during scheduling.

Should cdk8s-plus configure this by default?

See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#more-practical-use-cases

Additional questions

  • Does kubernetes do this by default? try to?
@iliapolo iliapolo added priority/p1 Should be on near term plans effort/small 1 day tops feature-request New/Enhanced functionality wanted labels Jun 29, 2022
@vinayak-kukreja vinayak-kukreja mentioned this issue Sep 20, 2022
Merged
mergify bot pushed a commit that referenced this issue Sep 29, 2022
@vinayak-kukreja
feat(workload): spread property for easy hostname and zone spre…
0847398 
…ading (#1176)

Following Kubernetes [guidance](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/#internal-default-constraints) to spread pods across nodes and zones for a workload. Adding a default spread property to workloads. 

Resolves #890

Signed-off-by: Vinayak Kukreja <[email protected]>
@mergify mergify bot closed this as completed in #1176 Sep 29, 2022
cdk8s-automation pushed a commit that referenced this issue Sep 29, 2022
@vinayak-kukreja
feat(workload): spread property for easy hostname and zone spre…
d07ef06 
…ading (#1176)

Following Kubernetes [guidance](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/#internal-default-constraints) to spread pods across nodes and zones for a workload. Adding a default spread property to workloads.

Resolves #890

Signed-off-by: Vinayak Kukreja <[email protected]>
(cherry picked from commit 0847398)
Signed-off-by: Vinayak Kukreja <[email protected]>
cdk8s-automation pushed a commit that referenced this issue Sep 29, 2022
@vinayak-kukreja
feat(workload): spread property for easy hostname and zone spre…
2b60586 
…ading (#1176)

Following Kubernetes [guidance](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/#internal-default-constraints) to spread pods across nodes and zones for a workload. Adding a default spread property to workloads.

Resolves #890

Signed-off-by: Vinayak Kukreja <[email protected]>
(cherry picked from commit 0847398)
Signed-off-by: Vinayak Kukreja <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vinayak-kukreja vinayak-kukreja

Labels
effort/small 1 day tops feature-request New/Enhanced functionality wanted priority/p1 Should be on near term plans
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(workload): spread property for easy hostname and zone spreading cdk8s-team/cdk8s-plus
2 participants
@iliapolo @vinayak-kukreja