activeDeadlineSeconds is not work when build pod in pending status

[zhoufenqin]

I configure activeDeadlineSeconds:1800 in cnb image. when it tigger a build, there is a mount issue happen so the build pod is stay in Pending.
I wish the build can be set to Failed if the build pod can't work after 1800 seconds then I can try next build. But the pod keep stay in Pending for hours and block next builds.

The activeDeadlineSeconds may not realized in k8s pending pod, see here. So can the kpack-controller realize it? it can monitor the build create time and determine if make the build to ternimate status if the duration is too long

  ----     ------             ----                      ----                -------
  Warning  FailedScheduling   16m (x43 over 3h40m)      default-scheduler   0/5 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/5 nodes are available: 5 Preemption is not helpful for scheduling..
  Normal   NotTriggerScaleUp  3m57s (x1889 over 5h20m)  cluster-autoscaler  pod didn't trigger scale-up: 3 pod has unbound immediate PersistentVolumeClaims