- Sort Score
- Result 10 results
- Languages All
Results 141 - 150 of 272 for upgrade (0.06 sec)
-
helm-releases/minio-3.1.6.tgz
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. 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...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 23 19:56:39 UTC 2021 - 14.5K bytes - Viewed (0) -
helm-releases/minio-3.0.1.tgz
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. 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...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 02 01:47:43 UTC 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-3.0.2.tgz
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. 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...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Sep 03 08:11:32 UTC 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-4.0.10.tgz
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. 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...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Aug 04 16:09:22 UTC 2022 - 19.2K bytes - Viewed (0) -
helm-releases/minio-4.0.14.tgz
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. 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...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Sep 05 01:06:49 UTC 2022 - 19.6K bytes - Viewed (0) -
helm-releases/minio-4.0.7.tgz
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. 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...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Jul 28 03:54:38 UTC 2022 - 18.6K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.30.md
- Kubeadm: used `ttlSecondsAfterFinished` to automatically clean up the `upgrade-health-check` Job that runs during upgrade preflighting. ([#122079](https://github.com/kubernetes/kubernetes/pull/122079), [@carlory](https://github.com/carlory))
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Oct 23 04:40:14 UTC 2024 - 309.1K bytes - Viewed (0) -
impl/maven-core/src/main/java/org/apache/maven/execution/MavenSession.java
} @Deprecated public List<MavenProject> getSortedProjects() { return getProjects(); } @Deprecated // // Used by Tycho and will break users and force them to upgrade to Maven 3.1 so we should really leave // this here, possibly indefinitely. // public RepositoryCache getRepositoryCache() { return null; } @Deprecated
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 16.6K bytes - Viewed (0) -
architecture/ambient/ztunnel-cni-lifecycle.md
Alternatively, we could send the GOAWAY prior to the pod termination (assuming this allows existing and new connections to function still). ## Ztunnel Shutdown/Upgrade/Restart This could be upgrading to a new version, or changing some part of the DaemonSet spec, etc. ### Ztunnel Shutdown Requirements Our high level requirement is to minimize traffic disruption.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Jul 17 23:10:17 UTC 2024 - 9.4K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.16.md
- [Server binaries](#server-binaries-2) - [Node binaries](#node-binaries-2) - [Changelog since v1.16.12](#changelog-since-v11612) - [Urgent Upgrade Notes](#urgent-upgrade-notes) - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade) - [Changes by Kind](#changes-by-kind-2) - [Bug or Regression](#bug-or-regression-2) - [Dependencies](#dependencies-2) - [Added](#added-2)
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu Feb 11 10:00:57 UTC 2021 - 345.2K bytes - Viewed (0)