convertApplicationToHelmRelease now builds the HelmRelease spec from ReleaseConfig instead of hardcoding values, bringing it in lockstep with cozystack-operator's PackageReconciler.buildHelmReleaseSpec (PR #2509). The drift between the two HelmRelease-generating paths was the rationale for this follow-up. Changes to the generated spec: - Spec.Interval reads ReleaseConfig.HelmReleaseInterval (was hardcoded 5m). - Spec.MaxHistory set as &maxHistory pointer from ReleaseConfig.HelmReleaseMaxHistory; 0 survives as pointer-to-0 (unlimited per Helm semantics) - mirrors the operator's TestBuildHelmReleaseSpecZeroMaxHistory. - Install.Strategy{Name: RetryOnFailure, RetryInterval} replaces Install.Remediation{Retries: -1}. Same for Upgrade.Strategy. Functionally equivalent to "retry forever, never remediate" for the api-side path (which also never relied on remediation firing) but decouples failed-install retry timing from Spec.Interval. - Install.Remediation / Upgrade.Remediation stay nil: helm-controller's XValidation rejects RetryOnFailure + RetryInterval alongside a Remediation entry, so reintroducing Retries:-1 "for safety" would silently break every HR. Install/Upgrade.Timeout precedence: - per-Application HelmInstallTimeout (annotation-driven) wins when non-zero (preserves the kubernetes-rd opt-in path); - otherwise HelmReleaseInstallTimeout / HelmReleaseUpgradeTimeout globals apply; - when both are zero, the field stays nil and flux defaults apply (preserves the legacy code path for tests that hand-construct ReleaseConfig without populating the new globals). Tests: - rest_timeout_test.go: Remediation.Retries == -1 assertions replaced with Strategy.Name == RetryOnFailure + Remediation == nil, matching the operator's spec test. - rest_helmrelease_spec_test.go: new file mirroring TestBuildHelmReleaseSpec / TestBuildHelmReleaseSpecZeroMaxHistory from internal/operator/package_reconciler_test.go, plus a third case asserting per-Application HelmInstallTimeout overrides the global Install/Upgrade timeout defaults. Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
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 Feature Requests please use the Discussion's Feature Request section.
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.
