samox73

using ```yaml common: .... storage: s3: access_key_id: ACCESS_KEY bucketnames: mybucketname endpoint: s3.eu-central-1.amazonaws.com region: eu-central-1 s3forcepathstyle: true secret_access_key: URI_ENCODED_SECRET_KEY ``` does not seem to work either EDIT: just to be clear,...

@pbn4 yes, here's the configuration I used. It's taken from a pulumi project, that's why its typescript, but should transfer to YAML: ```ts values: { loki: { config: { common:...

@vartanbeno has this project been abandoned? I am also getting the ```html reddit's awesome and all, but you may have a bit of a problem. we've seen far too many...

Has anyone made any progress on this issue except for the described workaround? This really cannot be a permanent fix, e.g. if the operator has to be recreated because of...

Running the wal-g upload command manually works without any errors ``` # envdir /run/etc/wal-e.d/env wal-g wal-push ../data/pg_wal/00000002.history INFO: 2022/10/06 12:23:12.494843 FILE PATH: 00000002.history.lz4 INFO: 2022/10/06 12:23:12.586170 FILE PATH: 000000010000000000000002.partial.lz4 INFO:...

So I figured out that for automatic backups to work, the env vars `AWS_ACCESS_KEY_ID` and `AS_SECRET_ACCESS_KEY` need to be set. I could not get it to work with the more...

Any update on this? A multi-domain option would make it also way easier to minimize downtime. Let's take an example: We have harbor running at `harbor.domain.org`. Now, we want to...

Is there any update on this? I'd like to switch over to ko from docker's buildx, but I'm also facing the problem of using ko with pre-existing projects where the...

As @unmarshall explained, having a fixed entrypoint poses the issue of breaking working systems and using ko as a drop-in replacement is not possible. Having the ability to change the...

We also need this, is there any progress?