VictoriaMetrics/lib/promscrape/discovery/yandexcloud
Aliaksandr Valialkin 4304950391
lib/promscrape/discovery/yandexcloud: follow-up for 070abe5c71
- Obtain IAM token via GCE-like API instead of Amazon EC2 IMDSv2 API,
  since it looks like IMDBSv2 API isn't supported by Yandex Cloud
  according to https://yandex.cloud/en/docs/security/standard/authentication#aws-token :

  > So far, Yandex Cloud does not support version 2, so it is strongly recommended
  > to technically disable getting a service account token via the Amazon EC2 metadata service.

- Try obtaining IAM token via GCE-like API at first and then fall back to the deprecated Amazon EC2 IMDBSv1.
  This should prevent from auth errors for instances with disabled GCE-like auth API.
  This addresses @ITD27M01 concern at https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5513#issuecomment-1867794884

- Make more clear the description of the change at docs/CHANGELOG.md , add reference to the related issue.

P.S. This change wasn't tested in prod because I have no access to Yandex Cloud.
It is recommended to test this change by @ITD27M01 and @vmazgo , who filed
the issue https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5513

Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6524
2024-07-16 17:58:40 +02:00
..
api.go lib/promscrape/discovery/yandexcloud: follow-up for 070abe5c71 2024-07-16 17:58:40 +02:00
instance.go lib/promscrape: optimize service discovery speed 2022-11-29 21:26:00 -08:00
instance_test.go lib: consistently use f-tests instead of table-driven tests 2024-07-09 22:40:50 +02:00
yandexcloud.go lib/promscrape/discovery/vultr: follow-up after 17e3d019d2 2024-07-05 17:40:03 +02:00