Skip to content

feat: add node affinity to Helm chart for improved pod scheduling #59

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.

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

Merged
merged 3 commits into from
Jun 13, 2024

Conversation

rowanruseler
Copy link
Contributor

Added node affinity rules to the Helm chart to ensure that pods are scheduled onto appropriate nodes based on specific criteria. This helps in optimizing resource utilization, enhancing performance, and maintaining workload balance across the cluster.

References:

Added node affinity rules to the Helm chart to ensure that pods are scheduled onto appropriate nodes based on specific criteria. This helps in optimizing resource utilization, enhancing performance, and maintaining workload balance across the cluster.

References:
- Kubernetes affinity and anti-affinity documentation: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
@rowanruseler
Copy link
Contributor Author

@ofekshenawa, @chayim Could you please take a moment to review my pull request? Your feedback would be greatly appreciated.

Bumped the version from 0.4.11 to 0.4.12, required since
redis-stack#61 adjusted the
version towards 0.4.11
@rowanruseler
Copy link
Contributor Author

@vladvildanov Could perhaps you take a moment to review my pull request? Your feedback would be greatly appreciated.

@vladvildanov vladvildanov merged commit 4e1f8e4 into redis-stack:main Jun 13, 2024
1 check passed
@rowanruseler
Copy link
Contributor Author

Thanks @vladvildanov

@vladvildanov
Copy link
Collaborator

@rowanruseler you're welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants