feat: add AWSEKSNODEGROUP entity type (NR-604119) - #3200
Merged
davidgonzalez-nr merged 3 commits intoSep 16, 2026
Merged
Conversation
New INFRA entity type for AWS EKS Nodegroups, mirroring the minimal AWSEC2VPC/AWSEC2SUBNET shape exactly (no synthesis block -- registered directly by aws-configuration-fetcher via CFT-scan discovery + CloudControl, not inferred from telemetry events; alertable: false, no golden/summary metrics -- CloudWatch metric-stream support for EKS Nodegroups is not being added in this pass, so there's nothing to chart yet). Lets aws-configuration-fetcher (1) register Nodegroup as a real entity when discovered via CFT scan, and (2) resolve a real GUID for it as the target of a Cluster->Nodegroup candidate relationship, matching the existing Cluster->VPC/Subnet pattern (see aws-configuration-fetcher PR https://source.datanerd.us/beyond/aws-configuration-fetcher/pull/377). Validated locally: `npm run check` in validator/ passes clean.
entityBot
previously requested changes
Aug 26, 2026
entityBot
left a comment
entityBot
left a comment
Collaborator
There was a problem hiding this comment.
beep boop bop.
I have found some errors processing these changes:
- No valid, approved ARB ticket found in the PR description. This PR has to be reviewed by the API Review Board, please include a link to the ticket of that review in the PR description. Check how to start the process here or reach
#api-review-boardchannel in case of doubts
entityBot
dismissed stale reviews from rpaliwal1997 and themself
September 14, 2026 06:04
Dismissing reviews
entityBot
requested changes
Sep 14, 2026
entityBot
left a comment
entityBot
left a comment
Collaborator
There was a problem hiding this comment.
beep boop bop.
I have found some errors processing these changes:
- ARB tickets not approved: NR-610550 (Status: In Review).
The review process is not handled by Entity Platform, reach#api-review-boardchannel in case of doubts
entityBot
approved these changes
Sep 16, 2026
davidgonzalez-nr
approved these changes
Sep 16, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
New INFRA entity type for AWS EKS Nodegroups, mirroring the minimal AWSEC2VPC/AWSEC2SUBNET shape exactly (no synthesis block -- registered directly by aws-configuration-fetcher via CFT-scan discovery + CloudControl, not inferred from telemetry events; alertable: false, no golden/summary metrics -- CloudWatch metric-stream support for EKS Nodegroups is not being added in this pass, so there's nothing to chart yet).
Lets aws-configuration-fetcher (1) register Nodegroup as a real entity when discovered via CFT scan, and (2) resolve a real GUID for it as the target of a Cluster->Nodegroup candidate relationship, matching the existing Cluster->VPC/Subnet pattern (see aws-configuration-fetcher PR https://source.datanerd.us/beyond/aws-configuration-fetcher/pull/377).
Validated locally:
npm run checkin validator/ passes clean.Relevant information
Api Review Board (ARB)
Pull requests with changes to this repository might need to be linked with an ARB ticket, which has to be approved before merging.
If you are an external contributor please contact New Relic Support.
What definition changes require ARB and which do not? Guide here.
If you are new to ARB process also check this.
ARB Jira ticket:
https://new-relic.atlassian.net/browse/NR-610550
Checklist
identifierwill be unique and valid.