The knative operator and operator webhook require that several configmaps and secrets be present before the application is launched. If they launch without these resources, they fail immediately (<1s).
Because these processes are launched via Pebble, we might expect that Pebble would auto-restart these processes if they die. However, Pebble sees a quick exit (exit in <1s) not as a start and fail but instead as if the processes has not started at all (see here), putting the process in an inactive state that cannot be easily recovered (this is discussed more here. We should handle this somehow.
The knative operator and operator webhook require that several configmaps and secrets be present before the application is launched. If they launch without these resources, they fail immediately (<1s).
Because these processes are launched via Pebble, we might expect that Pebble would auto-restart these processes if they die. However, Pebble sees a quick exit (exit in <1s) not as a start and fail but instead as if the processes has not started at all (see here), putting the process in an inactive state that cannot be easily recovered (this is discussed more here. We should handle this somehow.