You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this PR, we're adding a new read_timeout settings which should be exposed in our CRDs.
### Definition of Done
- [ ] the `read_timeout` setting is added to the [Storage](https://github.com/k8ssandra/k8ssandra-operator/blob/main/apis/medusa/v1alpha1/medusa_types.go#L28) struct and mapped appropriately in medusa.ini
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-17
The text was updated successfully, but these errors were encountered:
Is there some information about when it will be treated ?
It's blocking the upgrade of the k8ssandra operator for us as since the PR merged on medusa side was integrated in the operator, it makes the restoration process of the cluster fail because of big files that cannot be downloaded.
I already posted a comment on the merge PR on medusa side (thelastpickle/cassandra-medusa#763 (comment)) as I do not know what is the best solution on this issue: Rollback the read_timeout update for gcp case on medusa or implement the support of the timeout on the operator side.
In this PR, we're adding a new
read_timeout
settings which should be exposed in our CRDs.┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-17
The text was updated successfully, but these errors were encountered: