Alexey Artamonov f147b22d86 fix(backups): delete a MariaDB dump when its Backup is deleted
Deleting a MariaDB Backup left its dump in the bucket for good:
mariadb-operator's maxRetention prunes only from inside the next run of
the same prefix, and a Plan never deletes a Backup, so on the platform
bucket nothing else ever removes it.

Every run of an application writes under one prefix, so the key deleted
has to be proven to be this Backup's. It is the dump the Backup records,
or, for a Backup taken before dumps were recorded, the one the existing
ownership match attributes to its operator Backup. That match is
recorded on the Backup before the delete, so a retry deletes the same
key by name instead of matching again against a bucket that no longer
holds it. Without proof the Backup is released with a Warning and
nothing is deleted, the operator Backup included, since any later
attribution starts from it. The operator Backup is deleted only after
its dump, and the delete waits while a RestoreJob still restores from
the Backup.

The delete runs in the controller through the same minio client the
size probe uses, so it verifies TLS the way mariadb-operator did when
it wrote the dump. A dump on the platform bucket, which the operator
Backup names by its bucket and by the projected credentials Secret, is
reached through the platform's current endpoint and keys, still
trusting a CA the strategy pinned, so a Backup taken before the
endpoint moved is still deleted.

Platform credentials that cannot be read fall back to the ones the
operator Backup names. A failed delete holds the Backup and retries
with a Warning naming the skip-artifact-cleanup annotation, except in
a terminating namespace, where the Backup is released with a Warning
so it does not hold the namespace.

Assisted-by: LLM
Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
2026-11-06 17:24:29 +03:00
2025-10-08 09:43:34 +05:00
2024-02-08 12:04:32 +01:00

Cozystack Cozystack

GitHub Release Apache-2.0 License Commit activity OpenSSF Best Practices OpenSSF Scorecard CLOMonitor Support

Cozystack

Cozystack is a free and open-source platform and framework for building clouds.

Cozystack is a CNCF Sandbox project that was originally built and sponsored by Ænix.

With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.

Use Cozystack to build your own cloud or provide a cost-effective development environment.

Cozystack user interface

Use-Cases

Documentation

The documentation is located on the cozystack.io website.

Read the Getting Started section for a quick start.

If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.

Versioning

Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.

Contributions

Contributions are highly appreciated and very welcomed!

In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.

You are welcome to take on the fix yourself. Commits are used to generate the changelog, and their author will be referenced in it.

If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.

Community

You are welcome to join us in #cozystack, on either CNCF Slack (get an invite) or Kubernetes Slack (get an invite), in our Telegram group, and at our community meetings. Add them to your Google Calendar or iCal for convenience.

Project documents

Document What it covers
Governance How decisions are made and who makes them
Contributor Ladder How to grow from contributor to maintainer
Maintainers Who maintains the project
Code of Conduct What we expect of each other
Security Policy Reporting a vulnerability, and which releases get fixes
Adopters Who runs Cozystack in production
Roadmap Where the project is going

License

Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.

Commercial Support

A list of companies providing commercial support for this project can be found on official site.

Languages
Go 52%
Shell 34%
TypeScript 6.8%
Go Template 4.7%
Makefile 1.3%
Other 1.1%