-
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 AKS resource detector #3035
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3035 +/- ##
==========================================
- Coverage 91.56% 91.55% -0.01%
==========================================
Files 466 468 +2
Lines 22998 23022 +24
==========================================
+ Hits 21057 21078 +21
- Misses 1445 1447 +2
- Partials 496 497 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Behavior tested on AKS, Azure VM, and Docker Desktop k8s.
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.
looks good, just a couple nits. thanks!
processor/resourcedetectionprocessor/internal/azure/aks/aks_test.go
Outdated
Show resolved
Hide resolved
Loadtest failed :-| |
* Add AKS resource detector Behavior tested on AKS, Azure VM, and Docker Desktop k8s. * Address PR feedback
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
This change creates a resource detector for AKS. It checks for the presence of an env variable to determine if it's running on k8s, and attempts to retrieve data from the Azure IMDS endpoint to determine if it's running on Azure. If both conditions are met, it sets two Resource attributes. If not, no error is returned from the detector. Additionally, a change was made to the Azure detector to also not return an error when the IMDS endpoint is not available.
Behavior tested on AKS, Azure VM, and Docker Desktop k8s.