k8s support? #31
Labels
No Label
kind
bug
kind
build
kind
dependencies
kind
docs
kind
enhancement
kind
feature
kind
help wanted
kind
proposal
kind
refactor
related
act
related
environment
related
exec
related
gitea
related
workflow
reviewed
confirmed
reviewed
duplicate
reviewed
invalid
reviewed
needs feedback
reviewed
wontfix
reviewed
workaround
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/act_runner#31
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The current behavior is that action jobs can run in docker containers or in the same env of the act runner.
The jobs and the act runner are running on the same (virtual)machine/container.
So I think maybe we can support running action jobs in k8s.
Then we can separate the jobs from act runner, and use cloud container PaaS such as Azure Container Instance to run jobs?
This requires writing a separate backend that handles K8S properly. I'm sure we won't mind adding it to
act
itselfIf you're just looking for the runner to work in Kubernetes, take a look at #207. It's got a dind deployment spec in it that will work for you. Also #208 has a rootless container that can be deployed into Kubernetes without the dind mess.
@pj In regards to your comment, is this what needs to happen to remove the dependency on Docker?
I have no idea what you are talking about
My mistake @pj. I misread your response and believed that you were talking about removing Acts requirement on docker. Cheers anyways.
Update a related discussion(maybe): https://github.com/go-gitea/gitea/issues/29567