Releases: criteo/s3-probe
Releases · criteo/s3-probe
Fixes release v1.8.8
v1.8.9 Pushgateway destination regexp should only split the destination tag …
Manage pushgateway destination that are pure endpoints
Moving to LB, we don't need to put pushgateway destination as consul services. For now stay retro compatible.
Use static frontend instead of consul service
Instead of fetching consul services, we provide a list of static endpoints to monitor (the probe wills till discover s3-gateway tags though)
Use static frontend instead of consul service
Instead of fetching consul services, we provide a list of static endpoints to monitor (the probe wills till discover s3-gateway tags though)
Use static frontend instead of consul service
Instead of fetching consul services, we provide a list of static endpoints to monitor (the probe wills till discover s3-gateway tags though)
Use static frontend instead of consul service
Instead of fetching consul services, we provide a list of static endpoints to monitor (the probe wills till discover s3-gateway tags though)
cleanup of temporary objects
What's Changed
- Bump github.com/prometheus/client_golang from 1.11.0 to 1.11.1 by @dependabot in #28
- probe: implement cleanup of temporary objects by @pgoron in #29
New Contributors
- @dependabot made their first contribution in #28
Full Changelog: v1.8.2...v1.8.3
v1.8.2: Use only passing service for discovery
If we deploy a wrong change, it will still be detected by the probe as the service will be present but red. This commit will make sure the probe only use passing endoints
v1.8.1: Merge pull request #25 from criteo/fix-build
Fix duplicated release jobs
v1.7.10
Regenerating artifacts