Our first approach is to reduce the number of replicas to only what is essential by using the following command:

ab443838-9b3e-4811-b287-74e417a9@Azure:~$ kc scale --replicas=1 deployment/frontend
deployment.extensions/frontend scaled
ab443838-9b3e-4811-b287-74e417a9@Azure:~$ kc scale --replicas=1 deployment/redis-slave
deployment.extensions/redis-slave scaled

Let's check the events as follows:

kc get events
LAST SEEN   FIRST SEEN   COUNT     NAME                                           KIND      SUBOBJECT   TYPE      REASON             SOURCE              MESSAGE
1m          5h           1973      redis-slave-b58dc4644-tcl2x.1574e9eadbae3e88   Pod                   Warning   FailedScheduling   default-scheduler   0/2 nodes are available: 1 Insufficient cpu, 1 node(s) were not ready, 1 node(s) were out of disk space.

Despite reducing the replicas, we still get the error message. The VM that we are running simply does not have the horsepower to run these apps.