We're moving the fork of Kopia that Klio builds against under the cloudnative-pg org, so it's maintained as part of the project.
What's been done
- Forked
kopia/kopia into cloudnative-pg/kopia.
- Created a
klio branch on the new fork, starting from the latest upstream master, with the three Klio-specific patches from leonardoce/kopias klio-20260525 branch rebased on top:
- mTLS authentication
--tags support- gRPC stream interceptor for session-error logging
- Verified the rebased branch builds and passes
go vet cleanly.
What's left
- Update Klio to build against
cloudnative-pg/kopia (branch klio) instead of leonardoce/kopia (branch klio-20260525):
core/Dockerfile (the git clone step that bulilds the kopia binary)renovate.jsonAGENTS.md (Key Dependencies section)- a stale omment in
operator/test/e2e/otel_test.go
The existing e2e suite will act as the regression check for this switch.
We're moving the fork of Kopia that Klio builds against under the
cloudnative-pgorg, so it's maintained as part of the project.What's been done
kopia/kopiaintocloudnative-pg/kopia.kliobranch on the new fork, starting from the latest upstreammaster, with the three Klio-specific patches fromleonardoce/kopiasklio-20260525branch rebased on top:--tagssupportgo vetcleanly.What's left
cloudnative-pg/kopia(branchklio) instead ofleonardoce/kopia(branchklio-20260525):core/Dockerfile(thegit clonestep that bulilds thekopiabinary)renovate.jsonAGENTS.md(Key Dependencies section)operator/test/e2e/otel_test.goThe existing e2e suite will act as the regression check for this switch.