feat: support lifecycle hooks on the SonarQube container #745
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PR adds the possibility to add lifecycle hooks to the SonarQube container. With the help of a postStart lifecycle hook it is possible to do an auto database migration by backing up the database and triggering the database migration. An init container does not work because it must terminate before the application container is started, and a sidecar container terminating after the database migration gets automatically restarted. Using a job has the drawback that it becomes difficult to ensure that the job is always started when the SonarQube pod starts. A postStart lifecycle hook is the perfect and lightweight solution for this kind of use case.
Please ensure your pull request adheres to the following guidelines:
CHANGELOG.mdfile of the respected chart as well as theChart.yaml