HangfireIO / HangfireIO/Hangfire
Impossible to run in Kubernetes properly
Open
t: question
- Dominant language
- C#
- Stars
- 10.1k
- Forks
- 1.8k
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 1
Description
Hi guys. I want to run ASP.NET Core and schedule background tasks with hangfire. However for some reason it kills the main process (with PID 1 in container) and thus Kubernetes "thinks" that the container has crashed and sends sigterm.
Contributor guide
Research direction
No repository files or tests are named. Start by reproducing an ASP.NET Core application using Hangfire in Kubernetes, then inspect the container's PID 1 lifecycle and signal handling. Done means the application can run background tasks without Kubernetes treating the container as crashed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, kubernetes
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100