Transition from rollingUpdate to Recreate hits a kubectl shortcoming
We use the recreate strategy when a volume is defined.
https://github.com/kubernetes/kubernetes/issues/24198
strategy:
rollingUpdate: null
type: Recreate
Seems to solve the issue with kubectl apply.
It doesn't seem to work in Flux though. Todo: test case with Flux, report issue in Flux if doesn't work
Good First Issue
How is it so?
The bug is well described in the linked Kubernetes issue. That issue is resolved, and kubectl is able to propagate null fields to the api server. The task is to test that behavior, and then test again when flux does the apply
@laszlocph is there a linked issue for the flux-apply ?
I never pursued this further.