</mime-type>
  <mime-type type="application/vnd.pwg-multiplexed"/>
  <mime-type type="application/vnd.pwg-xhtml-print+xml"/>
  <mime-type type="application/vnd.qualcomm.brew-app-res"/>
  <mime-type type="application/vnd.quark.quarkxpress">
    <glob pattern="*.qxd"/>
    <glob pattern="*.qxt"/>
    <glob pattern="*.qwd"/>
    <glob pattern="*.qwt"/>
    <glob pattern="*.qxl"/>
    <glob pattern="*.qxb"/>
  </mime-type>

takes an optional flag "--maximum-startup-sequence-duration". This allows you to explicitly define an upper bound on the apiserver startup sequences before healthz begins to fail. By keeping the kubelet liveness initial delay short, this can enable quick kubelet recovery as soon as we have a boot sequence which has not completed in our expected time frame, despite lack of completion from longer boot sequences (like RBAC). Kube-apiserver behavior when the value of this flag is zero is backwards compatible...

### Promoted core CSI Migration to Stable