feat: improve availability of HyperDX pods #75
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 08897df The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
|
thanks for the contribution @jspranger ! |
teeohhem
approved these changes
Jul 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces several optional configurations aimed at improving the availability and resilience of HyperDX pods.
Additions:
• PodDisruptionBudget (disabled by default):
Ensures a minimum number of replicas remain available during voluntary disruptions. Defaults to a minimum of 1 replica but is configurable.
• Optional priorityClassName support:
Enables better control over pod scheduling and preemption by allowing assignment of a custom priority class.
• Optional resource requests and limits:
Defines resources for the app container to:
– Guarantee the pod receives the required CPU/memory.
– Prevent resource-hungry containers from affecting node stability.
• Optional topologySpreadConstraints:
Allows pods to be distributed across different nodes (using a specified topology key), reducing the impact of node-level failures.
All features are disabled or conservative by default to maintain backward compatibility and allow for gradual opt-in.