wait4x icon indicating copy to clipboard operation
wait4x copied to clipboard

S3 support

Open mircea-pavel-anton opened this issue 11 months ago • 3 comments

It would be nice to have the ability to wait for an s3 endpoint as well, optionally also validating credentials

mircea-pavel-anton avatar Mar 10 '25 18:03 mircea-pavel-anton

Hey @mircea-pavel-anton, thanks for your suggestion! Could you clarify what you mean by "S3 endpoint"? Are you referring to waiting for the existence of a bucket or a specific file/object? Could you please elaborate a bit more?

atkrad avatar Mar 10 '25 23:03 atkrad

Hi, @atkrad

I will explain the usecase I had in mind, hopefully that clears it up a bit, as I was quite short with my initial proposal 😅

So the idea is as follows:

  • I have a Kubernetes cluster in which I run my workloads
  • I self host a MinIO instance in this cluster to provide S3-compatible endpoints for my apps
  • I would like to have an init container for my apps to:
  1. wait for that S3 endpoint to be available (i.e. minio is up and running)
  2. Wait for a given bucket to be available
  3. Validate the given credentials

I think that point 1 can be accomplished right now via a TCP check on the S3 API endpoint. For points 2 and 3 I am not so sure

mircea-pavel-anton avatar Mar 11 '25 10:03 mircea-pavel-anton

While the motto of the project is to wait for anything, this sounds like it's getting in the weeds of waiting on one of a myriad of AWS services. Having to include the AWS SDK to do this S3 check I think would bloat the executable by a lot.

This use case sounds like would be most appropriate for using the AWS CLI image, especially if it's just for a quick check in an init container.

erhhung avatar Aug 09 '25 08:08 erhhung