-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Add EKS cluster name detection #27408
Conversation
processor/resourcedetectionprocessor/internal/aws/eks/metadata.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall, but someone from AWS should take a look.
processor/resourcedetectionprocessor/internal/aws/eks/detector.go
Outdated
Show resolved
Hide resolved
processor/resourcedetectionprocessor/internal/aws/eks/detector.go
Outdated
Show resolved
Hide resolved
processor/resourcedetectionprocessor/internal/aws/eks/detector.go
Outdated
Show resolved
Hide resolved
processor/resourcedetectionprocessor/internal/aws/eks/detector.go
Outdated
Show resolved
Hide resolved
processor/resourcedetectionprocessor/internal/aws/eks/detector.go
Outdated
Show resolved
Hide resolved
processor/resourcedetectionprocessor/internal/aws/eks/detector.go
Outdated
Show resolved
Hide resolved
processor/resourcedetectionprocessor/internal/aws/eks/detector.go
Outdated
Show resolved
Hide resolved
274008a
to
9965c6b
Compare
Sorry for all of the updates here, linting is failing with OOM on the GitHub runners. I'm trying to find the best balance here of getting lint to complete successfully in the least amount of time possible. |
533f60c
to
c16d7de
Compare
.golangci.yml
Outdated
@@ -4,7 +4,7 @@ run: | |||
concurrency: 4 | |||
|
|||
# timeout for analysis, e.g. 30s, 5m, default is 1m | |||
timeout: 20m | |||
timeout: 100m |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this still necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My apologies, I should have marked this PR as draft earlier. All of the changes you marked were a part of my testing to determine the failure point in the linting process. I'm going to revert as many of these changes as possible, and mark the review as Ready for Review
when it's ready again.
Thanks for calling all of these out!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No apologies necessary :) happy to review when it's good to go
- Don't log and error, just error - Return error for empty cluster name - Return other information for other resources even if cluster name detection fails.
- Lint fix - Test fix: Move accessory methods into utils helper for testability.
- Cleanup config initialization - Use another possible tag for cluster name - Only get local EC2 instance tags
c16d7de
to
e6eb190
Compare
Looks like your linter config change didn't work out. I see |
Superseded by #28649. |
Description:
This enhancement detects the k8s cluster name in EKS. The solution uses EC2 instance tags to determine the cluster name, which means it will only work on EC2 (as noted in documentation updates).
Link to tracking Issue:
Resolves #26794
Testing:
Manual testing in an EKS cluster when running on EC2 instances.
Documentation:
Updated README and relevant metadata