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.
1.4 KiB
1.4 KiB
Security Policy
This policy outlines the commitment and practices of the go-openapi maintainers regarding security.
Supported Versions
| Version | Supported |
|---|---|
| O.x | ✅ |
Vulnerability checks in place
This repository uses automated vulnerability scans, at every merged commit and at least once a week.
We use:
Reports are centralized in github security reports and visible only to the maintainers.
Reporting a vulnerability
If you become aware of a security vulnerability that affects the current repository, please report it privately to the maintainers rather than opening a publicly visible GitHub issue.
Please follow the instructions provided by github to Privately report a security vulnerability.
Note
On Github, navigate to the project's "Security" tab then click on "Report a vulnerability".