Search Options

Results per page
Sort
Preferred Languages
Advance

Results 671 - 680 of 714 for exchange (0.13 sec)

  1. helm-releases/minio-3.1.6.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Sep 23 19:56:39 UTC 2021
    - 14.5K bytes
    - Viewed (0)
  2. helm-releases/minio-3.0.1.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Sep 02 01:47:43 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  3. helm-releases/minio-3.0.2.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Sep 03 08:11:32 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  4. helm-releases/minio-1.0.0.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Aug 20 22:30:54 UTC 2021
    - 13.5K bytes
    - Viewed (0)
  5. helm-releases/minio-1.0.1.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Fri Aug 20 22:32:29 UTC 2021
    - 13.5K bytes
    - Viewed (0)
  6. helm-releases/minio-1.0.3.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Tue Aug 24 19:04:07 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  7. helm-releases/minio-1.0.4.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Aug 25 02:12:51 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  8. helm-releases/minio-1.0.5.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Wed Aug 25 19:53:57 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  9. helm-releases/minio-2.0.0.tgz

    installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file....
    Registered: Sun Nov 03 19:28:11 UTC 2024
    - Last Modified: Thu Aug 26 07:36:46 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  10. doc/asm.html

    and the assembly must confirm this fact by executing the
    pseudo-instruction <code>NO_LOCAL_POINTERS</code>.
    Because stack resizing is implemented by moving the stack,
    the stack pointer may change during any function call:
    even pointers to stack data must not be kept in local variables.
    </p>
    
    <p>
    Assembly functions should always be given Go prototypes,
    Registered: Tue Nov 05 11:13:11 UTC 2024
    - Last Modified: Tue Nov 28 19:15:27 UTC 2023
    - 36.3K bytes
    - Viewed (0)
Back to top