New S3 Configuration breaks prior S3 configuration and is missing uploadPartSize #612
Comments
|
Sorry for this breaking change :/ I think your config should continue to work fine by just renaming the config file. |
provokateurin
added
bug
|
@provokateurin thanks for the quick response, I can try to open a PR but I'm no expert in helm charts and I can't test the change locally at the moment. |
|
🙇 sorry about that, @acidicX! I actually submitted nextcloud/docker#2271 upstream for these changes, but I'll submit one here as well now! |
|
In the meantime, you should be able to disable the default config being deployed by setting nextcloud:
defaultConfigs:
s3.config.php: falseCan you confirm if this works? Because if that doesn't work either, we should also try to fix that. Sorry again for the inconvenience regardless 🙏 |
4 tasks
|
Sorry for the rapid updates, but if #614 gets merged, it will close this Issue automatically. That doesn't mean we can't still help you if other things are still broken here though, so please just let us know if that's the case and we can reopen this issue for you if it gets closed 🙏 Update: We're going to wait till nextcloud/docker reviews/merges our upstream PR, nextcloud/docker#2271 before merging #614 |
|
@jessebot thanks for the fast reaction, I can confirm that the workaround ( |
|
Hello @jessebot , @acidicX ! nextcloud:
defaultConfigs:
s3.config.php: falseand it does not work for me. I try for 5.4.0 and 5.5.2 chart versions. I was able to fix it with renaming my s3 config file to: configs:
s33.config.php:Unfortunately it still needs to be fix. :( Essential part of my helm release file: defaultConfigs:
s3.config.php: false
swift.config.php: false
objectStore:
s3:
enabled: true
ssl: true
port: ***
region: ***
usePathStyle: true
autoCreate: true
existingSecret: nextcloud-values
secretKeys:
host: hostname
accessKey: key
secretKey: secret
bucket: bucket |
|
@MaksonHerson I'm sorry about that. Could you check and see if |
|
@jessebot this now does not work after #464 with sse_c_key specified or not. I tried both: |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe your Issue
I've used the S3 integration before "manually" via
configs.s3.config.php, now the helm chart upgrade (v5.4.0) fails because it's already definedLogs and Errors
Describe your Environment
Kubernetes distribution: k8s
Helm Version (or App that manages helm):
Helm Chart Version: 5.4.0
values.yaml:Additional context, if any
uploadPartSize, which is required to be set there for some reason on S3 storage, so I can't even switch to the new configuration styleThe text was updated successfully, but these errors were encountered: