- Sort Score
- Num 10 results
- Language All
Results 91 - 100 of 287 for pod1 (0.03 seconds)
-
helm-releases/minio-3.4.5.tgz
cluster for this to work. If you'd rather use `emptyDir`, disable PersistentVolumeClai by: ```bash helm install --set persistence.enabled=false minio/minio ``` > *"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."* Existing PersistentVolumeClai ---------- If a Persistent Volume Claim already exists, specify it during installation....
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Wed Jan 05 19:32:55 GMT 2022 - 15.2K bytes - Click Count (0) -
helm-releases/minio-3.5.3.tgz
cluster for this to work. If you'd rather use `emptyDir`, disable PersistentVolumeClai by: ```bash helm install --set persistence.enabled=false minio/minio ``` > *"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."* ### Existing PersistentVolumeClai If a Persistent Volume Claim already exists, specify it during installation. 1. Create...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Feb 13 23:43:44 GMT 2022 - 15.4K bytes - Click Count (0) -
helm-releases/minio-4.0.2.tgz
cluster for this to work. If you'd rather use `emptyDir`, disable PersistentVolumeClai by: ```bash helm install --set persistence.enabled=false minio/minio ``` > *"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."* ### Existing PersistentVolumeClai If a Persistent Volume Claim already exists, specify it during installation. 1. Create...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Mon May 09 04:25:47 GMT 2022 - 18K bytes - Click Count (0) -
helm-releases/minio-4.0.3.tgz
cluster for this to work. If you'd rather use `emptyDir`, disable PersistentVolumeClai by: ```bash helm install --set persistence.enabled=false minio/minio ``` > *"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."* ### Existing PersistentVolumeClai If a Persistent Volume Claim already exists, specify it during installation. 1. Create...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Fri Jul 08 06:16:22 GMT 2022 - 18K bytes - Click Count (0) -
helm-releases/minio-3.6.6.tgz
cluster for this to work. If you'd rather use `emptyDir`, disable PersistentVolumeClai by: ```bash helm install --set persistence.enabled=false minio/minio ``` > *"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."* ### Existing PersistentVolumeClai If a Persistent Volume Claim already exists, specify it during installation. 1. Create...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Apr 17 21:46:44 GMT 2022 - 18.2K bytes - Click Count (0) -
helm-releases/minio-4.0.0.tgz
cluster for this to work. If you'd rather use `emptyDir`, disable PersistentVolumeClai by: ```bash helm install --set persistence.enabled=false minio/minio ``` > *"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."* ### Existing PersistentVolumeClai If a Persistent Volume Claim already exists, specify it during installation. 1. Create...
Created: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Tue Apr 26 02:41:39 GMT 2022 - 18K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.19.md
- Restores priority of static control plane pods in the cluster/gce/manifests control-plane manifests ([#89970](https://github.com/kubernetes/kubernetes/pull/89970), [@liggitt](https://github.com/liggitt)) [SIG Cluster Lifecycle and Node]
Created: Fri Dec 26 09:05:12 GMT 2025 - Last Modified: Wed Jan 05 05:42:32 GMT 2022 - 489.7K bytes - Click Count (0) -
impl/maven-cli/src/test/java/org/apache/maven/cling/invoker/mvnup/goals/UpgradeResultTest.java
@DisplayName("should create success result") void shouldCreateSuccessResult() { Path pom1 = Paths.get("pom.xml"); Path pom2 = Paths.get("module/pom.xml"); UpgradeResult result = new UpgradeResult( Set.of(pom1, pom2), // processed Set.of(pom1), // modified Set.of() // errors );Created: Sun Dec 28 03:35:09 GMT 2025 - Last Modified: Sat Jun 07 06:22:47 GMT 2025 - 9.4K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.15.md
### Alpha - You can now create a non-preempting Pod priority (NonPreemptingPriority). If set on a class, the pod will continue to be prioritized above queued pods of a lesser class, but will not preempt running pods. ([#74614](https://github.com/kubernetes/kubernetes/pull/74614), [@denkensk](https://github.com/denkensk))
Created: Fri Dec 26 09:05:12 GMT 2025 - Last Modified: Thu May 05 13:44:43 GMT 2022 - 278.9K bytes - Click Count (0) -
docs/pt/docs/tutorial/dependencies/dependencies-with-yield.md
Então, você pode procurar por essa exceção específica dentro da dependência com `except AlgumaExcecao`. Da mesma forma, você pode utilizar `finally` para garantir que os passos de saída são executados, com ou sem exceções. {* ../../docs_src/dependencies/tutorial007_py39.py hl[3,5] *} ## Subdependências com `yield` { #sub-dependencies-with-yield }Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 20:41:43 GMT 2025 - 14.2K bytes - Click Count (0)