-
Notifications
You must be signed in to change notification settings - Fork 544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Github Actions Workflow Talos in Docker & QEMU #8242
Comments
linking to slack: https://taloscommunity.slack.com/archives/CMARMBC4E/p1706824526485519 |
+1 |
Sounds good to me, probably also depends on #8141 And to have some feature parity with |
Ideally support for both RWO and RWX volumes. Out of all other mini/micro-k8s only minikube has support for RWX ones. |
Feature Request
Github Action Marketplace action feature for use in GHA CI testing Workflows.
Description
Currently, the kubernetes-sigs/kind local testing cluster action maintained as helm/kind-action by helm is the most common kubernetes ci testing kubernetes distribution on github. This is a kubernetes-in-docker only solution with various limitations due to kubernetes-in-docker behavior. Additionally, non-talos kubernetes testing in CI is not a 1:1 validation benchmark for k8s, iac, and app testing talos k8s target platform deliverables due to talos's unique features.
Moving forward with heavy talos focused projects would be greatly improved with a general public offering that offers talos in docker and talos in qemu github build and cleanup support on github actions marketplace.
This would greatly improve the GitOps development confidence and velocity and would offer a compelling use case benefit over and above the use case of Kind.
Additional Considerations
Currently I maintain the pulumi/devcontainer repository which offers a template repo boilerplate for starting new Pulumi projects. I would like to replace the helm/kind-actions usage in the included CI boilerplate with the future siderolabs/talos-actions as an early adopter.
The text was updated successfully, but these errors were encountered: