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
for testing issues, it can be nice to remove readiness and liveness probes completely, but for production I would expect the possibility to customize them 100%
I tried a first solution appending helm ifs statements to the container spec by treating it as a string. This will of course make the container spec impossible to be cast back to corev1.Containers , but as long as this step is done right before the conversion to string of the metadata I see no problems with it...
we do not use startup probes, but maybe this approach could be extended
for testing issues, it can be nice to remove readiness and liveness probes completely, but for production I would expect the possibility to customize them 100%
I tried a first solution appending helm ifs statements to the container spec by treating it as a string. This will of course make the container spec impossible to be cast back to corev1.Containers , but as long as this step is done right before the conversion to string of the metadata I see no problems with it...
we do not use startup probes, but maybe this approach could be extended
current implementation here #73
The text was updated successfully, but these errors were encountered: