Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Adapt SIGTERM handling in K8s solution for SecHub deployments with scheduler on #3470

Closed
de-jcup opened this issue Sep 30, 2024 · 0 comments · Fixed by #3527
Closed

Adapt SIGTERM handling in K8s solution for SecHub deployments with scheduler on #3470

de-jcup opened this issue Sep 30, 2024 · 0 comments · Fixed by #3527
Assignees
@sven-dmlr
Labels
operation server
Milestone
Server 2.3.0

Comments

@de-jcup
Copy link
Member

de-jcup commented Sep 30, 2024 •
edited
Loading

Situation

With

the SecHub server is now able suspend and resume jobs when it comes to SIGTERM from OS.

But in our sechub-solution the SIGTERM signal is currently not pushed through. So a K8s deployment does not lead to supsending.

Wanted

K8s deployment SIGTERM signal shall be sent to SecHub server application a K8s environment

Solution

Like done for PDS solutions, the SIGTERM signal shall be trapped inside the start.sh script and given to the java process
@sven-dmlr sven-dmlr changed the title Adopt SIGTERM handling in K8s solution for SecHub deployments with scheduler on Adapt SIGTERM handling in K8s solution for SecHub deployments with scheduler on Oct 14, 2024
@sven-dmlr sven-dmlr added this to the Server 2.3.0 milestone Oct 17, 2024
sven-dmlr added a commit that referenced this issue Oct 17, 2024
@sven-dmlr
implemented signal handling #3470
ed68afc 
- also updated Alpine version
- and fixed a typo
@sven-dmlr sven-dmlr mentioned this issue Oct 17, 2024
Merged
sven-dmlr added a commit that referenced this issue Oct 17, 2024
@sven-dmlr
Merge pull request #3527 from mercedes-benz/feature-3470-push-termina…
1ca472d 
…tion-signals-to-server-process

implemented signal handling for sechub server container #3470
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sven-dmlr sven-dmlr

Labels
operation server
Projects
None yet
Milestone
Server 2.3.0
Development

Successfully merging a pull request may close this issue.

implemented signal handling for sechub server container #3470 mercedes-benz/sechub
2 participants
@de-jcup @sven-dmlr