Ivan Okhotnikov
039bb7e180
Kvaps' review on #3178 flagged that this package's \`make update\` target does \`rm -rf charts && helm pull cowboysysop/vertical-pod- autoscaler --version 11.1.1\` with no re-apply step. Any local edits to the vendored subchart were therefore one \`make update\` away from vanishing without warning — exactly what the fluxcd-operator package pre-empts via a \`patches/*.diff\` re-apply loop after the helm pull. Adopt the same convention here: * New file \`patches/cert-manager-admission-tls.diff\` capturing all four modifications the cert-manager path makes to the vendored subchart — the new \`certificate.yaml\` template, the checksum/tls-secret + new checksum/tls-cert annotation gating on the admission-controller Deployment, the certManagerEnabled guard on the legacy \`tls-secret.yaml\`, and the new \`certManagerEnabled: true\` default in the subchart values. * Makefile \`update\` target now runs \`patch --no-backup-if-mismatch -p1 < patches/*.diff\` after the helm pull, so a future upstream bump (or a routine \`make update\` today) re-applies the cozystack modifications over the freshly-fetched vendored files and leaves the chart in the same state git tracks. Verified end-to-end: with the on-disk chart intact I ran cp -r charts/vertical-pod-autoscaler /tmp/reference rm -rf charts helm pull cowboysysop/vertical-pod-autoscaler --untar --untardir charts --version 11.1.1 patch --no-backup-if-mismatch -p1 < patches/cert-manager-admission-tls.diff diff -r charts/vertical-pod-autoscaler /tmp/reference The diff is empty — \`make update\` now produces a byte-identical tree to what git has right now, and the 15 helm-unittest cases still pass unchanged. Signed-off-by: Ivan Okhotnikov <ivan.okhotnikov@aenix.io>
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.