Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1251 - 1260 of 1,281 for Mach (0.06 sec)

  1. CHANGELOG/CHANGELOG-1.8.md

    * Fixes an issue with RBAC reconciliation that could cause duplicated subjects in some bootstrapped rolebindings on each restart of the API server. ([#53239](https://github.com/kubernetes/kubernetes/pull/53239), [@enj](https://github.com/enj))
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Tue Feb 20 15:45:02 UTC 2024
    - 312.2K bytes
    - Viewed (0)
  2. helm-releases/minio-3.5.7.tgz

    minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Feb 20 08:55:08 UTC 2022
    - 17.6K bytes
    - Viewed (0)
  3. helm-releases/minio-3.5.8.tgz

    minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Feb 27 06:44:38 UTC 2022
    - 17.7K bytes
    - Viewed (0)
  4. helm-releases/minio-3.6.1.tgz

    minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Tue Mar 15 00:13:17 UTC 2022
    - 17.9K bytes
    - Viewed (0)
  5. helm-releases/minio-3.5.4.tgz

    minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Mon Feb 14 06:04:53 UTC 2022
    - 17.2K bytes
    - Viewed (0)
  6. helm-releases/minio-3.5.5.tgz

    minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Feb 16 19:44:53 UTC 2022
    - 17.2K bytes
    - Viewed (0)
  7. helm-releases/minio-3.6.6.tgz

    minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Apr 17 21:46:44 UTC 2022
    - 18.2K bytes
    - Viewed (0)
  8. helm-releases/minio-4.0.0.tgz

    minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Tue Apr 26 02:41:39 UTC 2022
    - 18K bytes
    - Viewed (0)
  9. helm-releases/minio-4.0.6.tgz

    minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Sun Jul 24 03:34:14 UTC 2022
    - 18.4K bytes
    - Viewed (0)
  10. CHANGELOG/CHANGELOG-1.12.md

    - Reporting E2E conformance test results to TestGrid from every cloud provider (in collaboration with SIG Testing & SIG Release)
    - Defining minimum required documentation from each cloud provider which includes (in collaboration with SIG Docs):
      - example manifests for the kube-apiserver, kube-controller-manager, kube-schedule, kubelet, and the cloud-controller-manager
    Registered: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Thu Feb 06 06:04:15 UTC 2020
    - 293.8K bytes
    - Viewed (0)
Back to top