3 ms·
I think it’s fair to not call it equivalent because of that, but it’s also fair to acknowledge what is unsupported is pretty power user level stuff for the most
by SOLAR_FIELDS 3y ago
I think it’s fair to not call it equivalent because of that, but it’s also fair to acknowledge what is unsupported is pretty power user level stuff for the most part. I used spaces in s3 compatibility for a few use cases and never ran into the problem that what I was trying to do was unsupported. Granted I was not trying to do fancy things, but still.
Some examples of things that I used the S3 compat for that worked just fine:
- terraform backend
- velero backups
- log store for prometheus/promtail
- docker pull through cache
- dijksterhuis 3y agoYep, for basic object storage via boto3 etc. it mostly works fine. hence why I called it a nit pick. There are additional interop things like Apache Spark <--> Spaces that don't work like Spark <--> AWS S3 (endpoint URL config issue which I lost the will to sort out as it was quicker to just use AWS S3 :shrug:).