- Sort Score
- Result 10 results
- Languages All
Results 571 - 580 of 773 for wantSz (0.06 sec)
-
helm-releases/minio-4.0.9.tgz
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. Update these fields if you'd like to use a different strategy. ### Configuration...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Aug 03 06:10:44 UTC 2022 - 18.6K bytes - Viewed (0) -
helm-releases/minio-4.0.4.tgz
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. Update these fields if you'd like to use a different strategy. ### Configuration...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Jul 14 04:44:23 UTC 2022 - 18.2K bytes - Viewed (0) -
helm-releases/minio-3.1.2.tgz
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. Update these fields if you'd like to use a different strategy. Configuration ----------...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sat Sep 18 04:26:47 UTC 2021 - 14.4K bytes - Viewed (0) -
helm-releases/minio-3.1.4.tgz
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. Update these fields if you'd like to use a different strategy. Configuration ----------...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Sep 20 05:30:22 UTC 2021 - 14.4K bytes - Viewed (0) -
helm-releases/minio-3.1.5.tgz
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. Update these fields if you'd like to use a different strategy. Configuration ----------...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Sep 22 16:52:01 UTC 2021 - 14.4K bytes - Viewed (0) -
helm-releases/minio-4.1.0.tgz
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. Update these fields if you'd like to use a different strategy. ### Configuration...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Oct 24 20:37:05 UTC 2022 - 20K bytes - Viewed (0) -
cmd/batch-handlers.go
} for id, job := range m.metrics { metrics.Jobs[id] = job.metric() } return metrics } // keep job metrics for some time after the job is completed // in-case some one wants to look at the older results. func (m *batchJobMetrics) purgeJobMetrics() { t := time.NewTicker(6 * time.Hour) defer t.Stop() for { select { case <-GlobalContext.Done(): return
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Oct 18 15:32:09 UTC 2024 - 62.2K bytes - Viewed (0) -
cni/README.md
1. Check k8s pod namespace against exclusion list (plugin config) - Config must exclude namespace that Istio control-plane is installed in (TODO: this may change, exclude at pod level is sufficient and we may want Istiod and other istio components to use ambient too) - If excluded, ignore the pod and return prevResult 1. Setup redirect rules for the pods: - Get the port list from pods definition, as well as annotations.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Jul 17 23:10:17 UTC 2024 - 10.5K bytes - Viewed (0) -
android/guava-tests/test/com/google/common/graph/AbstractStandardDirectedNetworkTest.java
* will silently add the missing nodes to the graph, then add the edge connecting them. We are not * using the proxy methods here as we want to test {@code addEdge} when the end-points are not * elements of the graph. */ @Test public void addEdge_nodesNotInGraph() { assume().that(graphIsMutable()).isTrue();
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Tue Jul 02 18:21:29 UTC 2024 - 20.8K bytes - Viewed (0) -
guava-tests/test/com/google/common/graph/AbstractStandardDirectedNetworkTest.java
* will silently add the missing nodes to the graph, then add the edge connecting them. We are not * using the proxy methods here as we want to test {@code addEdge} when the end-points are not * elements of the graph. */ @Test public void addEdge_nodesNotInGraph() { assume().that(graphIsMutable()).isTrue();
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Tue Jul 02 18:21:29 UTC 2024 - 21.2K bytes - Viewed (0)