"application/vnd.oma.poc.detailed-progress-report+xml",
				"application/vnd.oma.poc.final-report+xml",
				"application/vnd.oma.poc.groups+xml",
				"application/vnd.oma.poc.invocation-descriptor+xml",
				"application/vnd.oma.poc.optimized-progress-report+xml",
				"application/vnd.oma.xcap-directory+xml",
				"application/vnd.omads-email+xml",
				"application/vnd.omads-file+xml",

    This helps prevent "split brain" scenarios in clustered applications by
    ensuring that unreachable pods will not be presumed dead unless some
    "fencing" operation has provided one of the above indications.
  * For all other existing controllers except StatefulSet, this has no effect on
    the ability of the controller to replace pods because the controllers do not
    reuse pod names (they use generate-name).

  // +optional
  optional int32 healthCheckNodePort = 12;

  // publishNotReadyAddresses indicates that any agent which deals with endpoints for this
  // Service should disregard any indications of ready/not-ready.
  // The primary use case for setting this field is for a StatefulSet's Headless Service to
  // propagate SRV DNS records for its Pods for the purpose of peer discovery.

 - Conformance image is now built with Distroless. Users running Conformance testing should rely on container entrypoint instead of manual invocation to `/run_e2e.sh` or `/gorunner`, as they are now deprecated and will be removed in 1.25 release. Invoking `ginkgo` and `e2e.test` are still supported through overriding entrypoint (docker) or defining container `spec.command` (kubernetes). ([#9...

  <mime-type type="application/vnd.oma.poc.final-report+xml"/>
  <mime-type type="application/vnd.oma.poc.groups+xml"/>
  <mime-type type="application/vnd.oma.poc.invocation-descriptor+xml"/>
  <mime-type type="application/vnd.oma.poc.optimized-progress-report+xml"/>
  <mime-type type="application/vnd.oma.xcap-directory+xml"/>
  <mime-type type="application/vnd.omads-email+xml"/>