<mime-type type="application/vnd.etsi.iptvsad-bc+xml"/>
  <mime-type type="application/vnd.etsi.iptvsad-cod+xml"/>
  <mime-type type="application/vnd.etsi.iptvsad-npvr+xml"/>
  <mime-type type="application/vnd.etsi.iptvueprofile+xml"/>
  <mime-type type="application/vnd.etsi.mcid+xml"/>
  <mime-type type="application/vnd.etsi.sci+xml"/>
  <mime-type type="application/vnd.etsi.simservs+xml"/>

"text/html=html\napplication/msword=word\napplication/vnd.openxmlformats-officedocument.wordprocessingml.document=word\napplication/vnd.ms-excel=excel\napplication/vnd.ms-excel.sheet.2=excel\napplication/vnd.ms-excel.sheet.3=excel\napplication/vnd.ms-excel.sheet.4=excel\napplication/vnd.ms-excel.workspace.3=excel\napplication/vnd.ms-excel.workspace.4=excel\napplication/vnd.openxmlformats-officedocument.spreadsheetml.sheet=excel\napplication/vnd.ms-powerpoint=powerpoint\napplication/vnd.openxmlfor...

Backups are always a good precaution, particularly around upgrades, but this
upgrade has multiple known issues where the only remedy is to restore from
backup.

Also, please note:
- using `application/vnd.kubernetes.protobuf` as the media storage type for 1.6 is default but not required
- the ability to rollback to etcd2 can be preserved by setting the storage media type flag on `kube-apiserver`

  ```

    * If the serialization type is application/vnd.kubernetes.protobuf, and protobuf marshaling is not implemented for the requested API resource type, a '406 Not Acceptable is returned'.
    * If the serialization type is 'application/json':