unkin-agent
9da206dc7c
PVCs and CloudNativePG Clusters need S3 buckets and backup schedules
provisioned consistently. This operator watches the
backups.unkin.net/{schedule,destination} annotations on those objects and
provisions everything needed to back them up, with no new CRDs.
- Add a PVC controller that provisions cephrgw ObjectStoreUser/Bucket/BucketAccess,
auto-generates a restic repo-password Secret and creates a k8up Schedule scoped
to the PVC via spec.backup.volumes[].persistentVolumeClaim.claimName.
- Add a CNPG Cluster controller that provisions the same bucket stack, idempotently
patches spec.backup.barmanObjectStore (leaving a user-set destinationPath alone
with a Warning event) and creates a ScheduledBackup.
- Resolve destinations through a ConfigMap lookup table; requeue until the
BucketAccess is Ready before creating schedule resources; own-reference created
resources and retain bucket data by default.
- Add schedule-mapping helpers (k8up 5-field/shortcut pass-through, CNPG 6-field
seconds-first) and deterministic, length-bounded name derivation.
- Add unit tests (schedule mapping, name derivation, destination resolution) and
envtest controller tests for both paths, wiring the external CRDs into envtest.
- Add kubebuilder-generated RBAC, a Dockerfile (distroless/nonroot), Woodpecker
lint/test/build pipelines and a tag-triggered image push to the artifactapi
docker-internal registry, plus a version-bump Makefile and deploy manifests.
27 lines
956 B
Markdown
27 lines
956 B
Markdown
# How to contribute
|
|
|
|
We definitely welcome patches and contribution to this project!
|
|
|
|
### Tips
|
|
|
|
Commits must be formatted according to the [Conventional Commits Specification](https://www.conventionalcommits.org).
|
|
|
|
Always try to include a test case! If it is not possible or not necessary,
|
|
please explain why in the pull request description.
|
|
|
|
### Releasing
|
|
|
|
Commits that would precipitate a SemVer change, as described in the Conventional
|
|
Commits Specification, will trigger [`release-please`](https://github.com/google-github-actions/release-please-action)
|
|
to create a release candidate pull request. Once submitted, `release-please`
|
|
will create a release.
|
|
|
|
For tips on how to work with `release-please`, see its documentation.
|
|
|
|
### Legal requirements
|
|
|
|
In order to protect both you and ourselves, you will need to sign the
|
|
[Contributor License Agreement](https://cla.developers.google.com/clas).
|
|
|
|
You may have already signed it for other Google projects.
|