dotnet watch run does not forward SIGTERM to child process #20152
Labels
affected-few
This issue impacts only small number of customers
area-commandlinetools
Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI
bug
This issue describes a behavior which is not expected - a bug.
feature-dotnetwatch
This issue is related to the dotnet-watch command-line tool (now external)
investigate
severity-major
This label is used by an internal tool
Milestone
I am running an Orleans silo inside a local kubernetes cluster (using KinD). This is meant for local development. At the same time, I am using tilt and its "live update" functionality which essentially copies any modified files on my local filesystem to the container running my app. Doing so, I can run my program with
dotnet watch run
inside the kubernetes-hosted container relying on its file-watching capabilities to avoid unnecessary image rebuilds.However, rolling updates are necessary at times (testing scaling, for example) and I am having issues with the application not shutting down gracefully due to the fact that
dotnet watch run
does not forward theSIGTERM
sent by kubernetes (unless of course I'm missing something) for pod termination.This is not directly a Kubernetes-related issue, but I'm providing some context in case it helps anyone in some way. This is my current workaround unless someone has a better idea:
Program.cs
Dockerfile:
dev.py
The text was updated successfully, but these errors were encountered: