Description

<What were you trying to do that didn't work?>

I wanted to install kata with peerpods option enabled so i could work on creating the configmap and secret while nodes were being installed.  

Steps to reproduce

<What actions did you take to hit the bug?>
1. install operator
2. create kataconfig with peerpods: true
3. check kataconfig status

Expected result

<What did you expect to happen?>

Nodes would get installed for kata runtime.

Actual result

<What actually happened?>

Nothing happened.  kataconfig status showed

nodeCount: 0

nodeReady: 0

and didn't change (waited 5 minutes) 

Impact

<How badly does this interfere with using the software?>

Unexpected results.  We allow the user to do this.  It used to work this way in 1.4.  I think it is a reasonable workflow.

Env

<Where was the bug found, i.e. OCP build, operator build, kata-containers build, cluster infra, test case id>

OCP 4.14.1

OSC 1.5.0-34

Additional helpful info

<logs, screenshot, doc links, etc.>