Azure and GCP metadata decoration: integration tests

[mariomac]

It also improves the AWS EC2 tests by removing the need of mocking the AWS_EC2_METADATA_SERVICE_ENDPOINT variable. Now the fake IMDS is reachable at the standard 169.254.169.254 IP.

It also uses the low-level docker client to improve some aspects of docker_util_test:

• Enables container log reports after integration tests
• We need to assign the obi network alias to OBI so the Prometheus scraping work. The dockerutil high-level API required that the network was created shortly after the OBI container was created. This caused that sometimes it retrieved for metadata before the network was ready, causing the tests to fail.

[codecov]

Codecov Report

❌ Patch coverage is 53.33333% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 43.62%. Comparing base (7f9ab62) to head (469ebd1).
⚠️ Report is 8 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/appolly/meta/meta_node_cloud.go	53.33%	5 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1334      +/-   ##
==========================================
+ Coverage   43.56%   43.62%   +0.05%     
==========================================
  Files         307      307              
  Lines       32888    32967      +79     
==========================================
+ Hits        14329    14381      +52     
- Misses      17641    17663      +22     
- Partials      918      923       +5     

Flag	Coverage Δ
integration-test	21.78% <66.66%> (+<0.01%)	⬆️
integration-test-arm	0.00% <0.00%> (ø)
integration-test-vm-x86_64-5.15.152	0.00% <0.00%> (ø)
integration-test-vm-x86_64-6.10.6	0.00% <0.00%> (ø)
k8s-integration-test	2.34% <0.00%> (-0.02%)	⬇️
oats-test	0.00% <0.00%> (ø)
unittests	44.42% <66.66%> (+0.07%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mariomac]

Oh! Fun fact. Integration tests started to fail because OBI is taking the real Azure metadata from the GitHub runners instead of the mocked metadata providers.

[grcevski]

Looks like the new integration test is failing ...

[mariomac]

@grcevski concretely the Azure test, which works locally but in the GitHub runner, which works in Azure, it contacts to the real Azure metadata endpoint instead of the mocked endpoint. Unlike the other OTEL resource detectors, the Azure detector doesn't seem to allow overriding the Azure endpoint.

I need to have a look at the logs and see if I can configure better the Docker network. I have had to implement logging report in the new Go-based dockertest code.

[mariomac]

It seems that with the latest fixes to the dockerPool utility, all tests now passed. Re-running them again to discard any "lucky shot"

[grcevski]

Awesome! LGTM!