Is your feature request related to a problem? Please describe.
On systems with limited resources, the Nifi server container can take longer than usual to fully initialize. This leads to restarting the container while Nifi is starting.
Describe the solution you'd like
Have a way to configure in values.yaml the amount of time to permit the Nifi server container to start via a startup probe.
Describe alternatives you've considered
The initialDelaySeconds setting for the readiness/liveness probes was considered, but it is less flexible than a startup probe. Environments that can readily launch a Nifi server container should not be penalized by an extended initialDelaySeconds setting. A startup probe allows the system to be available faster OR on slow systems it allows enough time for the Nifi server to fully initialize.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe. On systems with limited resources, the Nifi server container can take longer than usual to fully initialize. This leads to restarting the container while Nifi is starting.
Describe the solution you'd like Have a way to configure in values.yaml the amount of time to permit the Nifi server container to start via a startup probe.
Describe alternatives you've considered The initialDelaySeconds setting for the readiness/liveness probes was considered, but it is less flexible than a startup probe. Environments that can readily launch a Nifi server container should not be penalized by an extended initialDelaySeconds setting. A startup probe allows the system to be available faster OR on slow systems it allows enough time for the Nifi server to fully initialize.
Additional context Add any other context or screenshots about the feature request here.