You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To reproduce, start the operator in terminal, outside the kubernetes cluster. And then press ctrl-c. Currently it prints something like "received SIGTERM, exiting gracefully", and what we want there [I guess :)] is to have ctrl-c to trigger the cancel function of the context, which in turn would make all the goroutines to quit, which would result in a graceful shut down of the operator (so it would print something like "context channel closed, exiting"). If something hangs, second ctrl-c would just shut down the operator right away.
Other way of reproducing is basically to run the operator inside the cluster, figure out its PID and kill it with SIGTERM as this is what would normally happen to the process when, for example, cluster or operating system is shutting down. But I'd say that running it outside the cluster and terminating it with ctrl-c is tons simpler.
See this.
This allows us to exit immediately if we receive two signals, in addition to exiting gracefully if we only receive one.
The text was updated successfully, but these errors were encountered: