## Summary - Add pre-creation cleanup of backend deployment/service and NFS pod/PVC in `run-kubernetes.sh`, so E2E test retries start fresh instead of reusing stuck resources from a failed attempt - Increase the tenant deployment wait timeout from 90s to 300s to handle CI resource pressure, aligning with other timeouts in the same function (control plane 4m, TCP 5m, NFS pod 5m) ## Context When `kubernetes-previous` (or `kubernetes-latest`) E2E test fails at the `kubectl wait deployment --timeout=90s` step, `set -eu` causes immediate exit before cleanup. On retry, `kubectl apply` sees the stuck deployment as "unchanged", making retries 2 and 3 guaranteed to fail against the same stuck pod. This was observed in [run 22076291555](https://github.com/cozystack/cozystack/actions/runs/22076291555) where `kubernetes-previous` failed 3/3 attempts while passing in 5/6 other recent runs. ## Test plan - [ ] E2E tests pass (kubernetes-latest and kubernetes-previous) - [ ] First clean run: `--ignore-not-found` cleanup commands are no-ops, no side effects - [ ] Retry after failure: stale deployment is deleted before re-creation, fresh pod is scheduled <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Improved test deployment reliability with more robust pre/post-test resource cleanup (including storage-related resources) to prevent leftovers from prior runs. * Made environment configuration handling more consistent to avoid misreads of cluster credentials. * Increased initialization and load balancer wait timeouts to reduce flaky failures during provisioning and validation. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Cozystack
Cozystack is a free PaaS 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.
