Risk consent must not block startup on Kubernetes

When installing 3rd party plugins via the init container that is provided by our helm chart the following scenario can be created: 

• Risk consent is not given
• a plugin is in the queue to be loaded 

this loading is hold by the missing consent, causing a small delay in the startup procedure. as a result of this small delay the startup probes are not hit as expected and SonarQube is killed by kubernetes as a failed start.

All of this is working as specified. Users who want to use 3rd party plugins are advised to enable persistence, to ensure the continuous existing of their plugins after a pod kill and increase the tolerance for the startup and liveness probes.