Description of problem:
pod status should be "DeadlineExceeded" instead of "Init:0/1" when initcontainer failed with DeadlineExceeded

Version-Release number of selected component (if applicable):
openshift v3.6.77
kubernetes v1.6.1+5115d708d7

How reproducible:
Always

Steps to Reproduce:
1. create a pod having active-deadline with initcontainer.
# cat pod-init-containers-deadline.yaml
apiVersion: v1
kind: Pod
metadata:
  name: init-deadline
spec:
  containers:
  - name: nginx
    image: nginx
    ports:
    - containerPort: 80
    volumeMounts:
    - name: workdir
      mountPath: /usr/share/nginx/html
  initContainers:
  - name: init
    image: centos:centos7
    command:
    - /bin/sh
    - "-c"
    - "sleep 30"
  activeDeadlineSeconds: 15
  volumes:
  - name: workdir
    emptyDir: {}

2. check the pod status before and after DeadlineExceeded
$ oc get pod

Actual results:
$ oc get pod
NAME            READY     STATUS     RESTARTS   AGE
init-deadline   0/1       Init:0/1   0          8s

# oc get pod
NAME            READY     STATUS     RESTARTS   AGE
init-deadline   0/1       Init:0/1   0          54s


Expected results:
since at time 8s, pod is running/pending, 
at time 54s, pod is failed,
I would expect user can get the difference  by pod status 
$ oc get pod
NAME            READY     STATUS     RESTARTS   AGE
init-deadline   0/1       Init:0/1   0          8s

# oc get pod
NAME            READY     STATUS             RESTARTS   AGE
init-deadline   0/1       DeadlineExceeded   0          54s
Additional info: