feat: add NodeClaim navigation support for Karpenter (#3658) #3676
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
Implement custom Enter key handler for Karpenter NodeClaim resources to navigate directly to the associated node. Previously, pressing Enter on a NodeClaim would only show its YAML description. Now it extracts the nodeName from status.nodeName and navigates to the corresponding node view. Resolves derailed#3658 Changes: - Add NodeClaimGVR constant for karpenter.sh/v1/nodeclaims - Create NodeClaim view with custom showNode handler - Register NodeClaim viewer in the custom viewers registry - Extract nodeName from NodeClaim status using unstructured access
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implement custom Enter key handler for Karpenter NodeClaim resources to
navigate directly to the associated node. Previously, pressing Enter on a
NodeClaim would only show its YAML description. Now it extracts the nodeName
from status.nodeName and navigates to the corresponding node view.
Resolves #3658
Changes
The implementation extracts nodeName from NodeClaim status using unstructured access and follows the same navigation pattern as other resources (e.g., Deployment → Pods).