minio-5.3.0.tar minio/Chart.yaml apiVersion: v1 appVersion: RELEASE.2024-04-18T19-09-19Z description: High Performance Object Storage home: https://min.io icon: https://min.io/resources/img/logo/MINIO_wordmark.png keywords: - minio - storage - object-storage - s3 - cluster maintainers: - email: ******@****.*** name: MinIO, Inc name: minio sources: - https://github.com/minio/minio version: 5.3.0 minio/values.yaml ## Provide a name in place of minio for `app:` labels ## nameOverride: "" ## Provide...

    /** The key of the message: Your search - <b>{0}</b> - did not match any documents. */
    public static final String LABELS_did_not_match = "{labels.did_not_match}";

    /** The key of the message: Try different keywords or check your spelling. */
    public static final String LABELS_did_not_match_suggestion = "{labels.did_not_match_suggestion}";

    /** The key of the message: Fess */

- To enhance usability and developer experience, CRD validation rules now support direct use of (CEL) reserved keywords as field names in object validation expressions.

- To enhance usability and developer experience, CRD validation rules now support direct use of (CEL) reserved keywords as field names in object validation expressions for existing expressions in storage, will fully support runtime in next release for compatibility concern. ([#126188](https://github.com/kubernetes/kubernetes/pull/126188), [@cici37](https://github.com/cici37))...

and with different keywords. In particular, we now match NumPy order as
`tf.split(value, num_or_size_splits, axis)`. * `tf.sparse_split` now takes
arguments in reversed order and with different keywords. In particular we now
match NumPy order as `tf.sparse_split(sp_input, num_split, axis)`. NOTE: we have
temporarily made `tf.sparse_split` require keyword arguments. * `tf.concat` now

  - `CustomPodDNS`
  - `HugePages`
  - `MountPropagation`
  - `PersistentLocalVolumes`
- CoreDNS: The following directives or keywords are deprecated and will be removed in v1.15:
  - `upstream` option of `kubernetes` plugin, becoming default behavior in v1.15.
  - `proxy` plugin replaced by `forward` plugin

## Removed and deprecated metrics

      },
      "mimetype": {
        "type": "keyword"
      },
      "parent_id": {
        "type": "keyword"
      },
      "role": {
        "type": "keyword"
      },
      "label": {
        "type": "keyword"
      },
      "virtual_host": {
        "type": "keyword"
      },
      "segment": {
        "type": "keyword"
      },
      "site": {
        "type": "keyword"

      "name": {
        "type": "keyword"
      },
      "password": {
        "type": "keyword"
      },
      "surname": {
        "type": "keyword"
      },
      "givenName": {
        "type": "keyword"
      },
      "employeeNumber" : {
        "type" : "keyword"
      },
      "mail" : {
        "type" : "keyword"
      },
      "telephoneNumber" : {
        "type" : "keyword"
      },
      "homePhone" : {

          },
          "groups" : {
            "type" : "keyword"
          },
          "homeDirectory" : {
            "type" : "keyword"
          },
          "homePhone" : {
            "type" : "keyword"
          },
          "homePostalAddress" : {
            "type" : "keyword"
          },
          "initials" : {
            "type" : "keyword"
          },

{
    "properties": {
      "type": {
        "type": "keyword"
      },
      "instanceId": {
        "type": "keyword"
      },
      "hostname": {
        "type": "keyword"
      },
      "name": {
        "type": "keyword"
      },
      "status": {
        "type": "keyword"
      },
      "targetInstanceId": {
        "type": "keyword"
      },
      "data": {
        "type": "text",
        "index": false