revert: remove chorus and dragonfly, restore kopiur direct to garage - #11677
Merged
Conversation
Reverts #11673, #11674, #11675 and #11676. The chorus proxy re-signs forwarded requests but passes streaming-signed (aws-chunked) bodies through unchanged, so every kopia PutObject over HTTP fails at Garage with "Invalid payload signature" (clyso/chorus#265). Signed-off-by: Devin Buhl <devin@buhl.casa>
Contributor
|
Warning
Note 2 changed · −55 removed: 57 resources across 6 apps · 1 CRD
konflate 0.6.3 · rendered |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts #11673, #11674, #11675 and #11676 in full:
chorus-system,dragonfly-system, the Dragonfly component, thechorctlmise entry, and the kopiur ClusterRepository/dependsOn changes. The ClusterRepository goes back toexpanse.internal:9000.Why: the chorus proxy re-signs forwarded requests but forwards streaming-signed (
aws-chunked) bodies verbatim, so the chunk signature chain no longer matches the new seed and Garage rejects every kopiaPutObjectover HTTP withInvalid payload signature. Reads work, writes fail; kopiur snapshots have been failing since the proxy entered the data path. Filed upstream as clyso/chorus#265.Post-merge: Flux prunes the chorus and dragonfly Kustomizations. The two namespaces stay (prune disabled by convention) and the two Dragonfly snapshot PVCs on
miroir-sloware left behind by the StatefulSet; delete them by hand if wanted. ThekopiurR2 bucket holds a partial seed and can be emptied.