myasnikovdaniil
fc592eff99
Fixes the false `promotion changed the container repository/digest set` that blocks #3904. `normalized_refs()` in `hack/verify-promoted-packages.sh` gives a host-less ref a repository equal to its own tag. `hack/lib/image-refs.sh` emits two entries per shape-3 map, the correctly joined ref plus shape 1's recursive scrape of the bare `tag: <tag>@sha256:...` scalar, and on that bare scalar `repo="${image%:*}"` is a no-op because there is no `/` and no `:` in it. Promotion rewrites exactly those tags, so `v1.6.2-rc.1` to `v1.6.2` shows up as six changed repositories whose digests are identical on both sides. `promote-retag.sh` never hits this because it drops host-less refs through its ownership filter, the verifier had no equivalent. Host-less refs now compare on digest alone, which is the whole of the container identity such a ref carries. Checked against the real published artifacts: before the fix 61 entries each side differing by those six pairs, after it 60 each side with the sets equal and 48 container digests identical. Two things this deliberately does not do, both written as comments at the fix. Not dropping host-less refs outright, because `packages/system/kuberture/values.yaml` carries an `image:` map with a `tag:` and no `repository:`, so shape 1 is the only rule that ever sees its digest and a drop would silently stop proving it unchanged. And not reusing `promote-retag.sh`'s `${REGISTRY}/` ownership filter, because the verify job's `REGISTRY` names the private build registry while both artifacts under comparison live on the public one, so that filter drops all 48 refs, and the emptiness guard above tests the raw collection rather than the filtered set, so the check would pass by comparing two empty sets. Second commit adds the fixture that was missing. The existing suite writes a host-bearing string and exercises a passing rc to stable rewrite, so it read as coverage while never building a shape-3 split map, which the library itself calls the dominant shape. Reverting the fix reddens the new case on the digest-set assertion, and replacing the fix with an outright skip of host-less refs makes the verifier exit 0 on a genuinely changed digest. Once this is on `release-1.6` the check on #3904 re-runs against this copy, so no `rc.2` re-cut is needed. `main` carries the same script and wants the same fix.
Cozystack
Cozystack is a free platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level 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.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
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 can express your intention to on the fix on your own. 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 our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
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.