I am trying to deploy on a minimal cluster and failing

How can I tweak the configuration to make the availability green?

My Input:

My application is a spring- angular (please suggest an easy way where I can deploy both)

My docker-compose created 2 containers. I pushed them to registry (tagged)

When deploying in Workload, I added 1 container after another, and clicked Deploy. The result error is above

Is there a file I need to create - a kind of yml or yaml etc?

kubectl get pods



> NAME                       READY   STATUS             RESTARTS   AGE
> nginx-1-d...7-2s6hb   0/2     CrashLoopBackOff   18         25m
> nginx-1-6..d7-7645w   0/2     CrashLoopBackOff   18         25m
> nginx-1-6...7-9qgjx   0/2     CrashLoopBackOff   18         25m

Events from describe

Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  17m                   default-scheduler  Successfully assigned default/nginx-1-5d...56xp4 to gke-cluster-huge-default-pool-b6..60-4rj5
  Normal   Pulling    17m                   kubelet            Pulling image "eu.gcr.io/p..my/py...my_appserver@sha256:479bf3e12ee2b410d730...579b940adc8845be74956f5"
  Normal   Pulled     17m                   kubelet            Successfully pulled image "eu.gcr.io/py..my/py...emy_appserver@sha256:479bf3e12ee2b4..8b99a178ee05e8579b940adc8845be74956f5" in 11.742649177s
  Normal   Created    15m (x5 over 17m)     kubelet            Created container p..my-appserver-sha256-1
  Normal   Started    15m (x5 over 17m)     kubelet            Started container p..emy-appserver-sha256-1
  Normal   Pulled     15m (x4 over 17m)     kubelet            Container image "eu.gcr.io/py...my/pya...my_appserver@sha256:479bf3e12ee2b41..e05e8579b940adc8845be74956f5" already present on machine
  Warning  BackOff    2m42s (x64 over 17m)  kubelet            Back-off restarting failed container