WHAT

Presuming that we stick with ingresscontrollers or ingress, and that it remains unshared with other services, we can delay the creation until a managedkafka is created.

WHY

There is a desire to minimize the footprint we create until there actually is a managedkafka installed.

HOW

It does not appear that MGDSTRM-11100 will be a good approach to achieve this as it would probably require defaulting the deployment replicas to 0 and neither custom metrics option is supported out of the box.  Instead we should change the fso ingresscontroller manager to immediately create the ingresscontrollers at startup.

DONE

We also need to ensure that creating them later, even it needs to trigger auto-scaling, won't be problem for existing pods in whatever machine pool the ingresscontrollers will use (currently the default).  Logically there should not be an issue, but services so far may be assuming that default resources are already available.