- Sort Score
- Result 10 results
- Languages All
Results 371 - 380 of 400 for declares (0.1 sec)
-
helm-releases/minio-4.0.9.tgz
install --set persistence.existingClaim=PVC_NAME minio/minio ``` ### NetworkPolicy To enable network policy for MinIO, install [a networking plugin that implements the Kubernetes NetworkPolicy spec](https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy#before-you-begin), and set `networkPolicy.enabled` to `true`. For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for *all* pods in the namespace:...
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-5.0.11.tgz
install --set persistence.existingClaim=PVC_NAME minio/minio ``` ### NetworkPolicy To enable network policy for MinIO, install [a networking plugin that implements the Kubernetes NetworkPolicy spec](https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy#before-you-begin), and set `networkPolicy.enabled` to `true`. For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for *all* pods in the namespace:...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Jun 21 19:29:09 UTC 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-5.0.12.tgz
install --set persistence.existingClaim=PVC_NAME minio/minio ``` ### NetworkPolicy To enable network policy for MinIO, install [a networking plugin that implements the Kubernetes NetworkPolicy spec](https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy#before-you-begin), and set `networkPolicy.enabled` to `true`. For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for *all* pods in the namespace:...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Jul 07 16:44:16 UTC 2023 - 20.4K bytes - Viewed (0) -
helm-releases/minio-5.0.13.tgz
install --set persistence.existingClaim=PVC_NAME minio/minio ``` ### NetworkPolicy To enable network policy for MinIO, install [a networking plugin that implements the Kubernetes NetworkPolicy spec](https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy#before-you-begin), and set `networkPolicy.enabled` to `true`. For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for *all* pods in the namespace:...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Jul 09 07:13:05 UTC 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-5.0.7.tgz
install --set persistence.existingClaim=PVC_NAME minio/minio ``` ### NetworkPolicy To enable network policy for MinIO, install [a networking plugin that implements the Kubernetes NetworkPolicy spec](https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy#before-you-begin), and set `networkPolicy.enabled` to `true`. For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for *all* pods in the namespace:...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Feb 13 10:37:23 UTC 2023 - 20.3K bytes - Viewed (0) -
helm-releases/minio-4.0.4.tgz
install --set persistence.existingClaim=PVC_NAME minio/minio ``` ### NetworkPolicy To enable network policy for MinIO, install [a networking plugin that implements the Kubernetes NetworkPolicy spec](https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy#before-you-begin), and set `networkPolicy.enabled` to `true`. For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for *all* pods in the namespace:...
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-5.1.0.tgz
install --set persistence.existingClaim=PVC_NAME minio/minio ``` ### NetworkPolicy To enable network policy for MinIO, install [a networking plugin that implements the Kubernetes NetworkPolicy spec](https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy#before-you-begin), and set `networkPolicy.enabled` to `true`. For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for *all* pods in the namespace:...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Mar 03 18:49:37 UTC 2024 - 21.3K bytes - Viewed (0) -
helm-releases/minio-5.2.0.tgz
install --set persistence.existingClaim=PVC_NAME minio/minio ``` ### NetworkPolicy To enable network policy for MinIO, install [a networking plugin that implements the Kubernetes NetworkPolicy spec](https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy#before-you-begin), and set `networkPolicy.enabled` to `true`. For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for *all* pods in the namespace:...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Apr 28 10:14:37 UTC 2024 - 21.7K bytes - Viewed (0) -
helm-releases/minio-4.1.0.tgz
install --set persistence.existingClaim=PVC_NAME minio/minio ``` ### NetworkPolicy To enable network policy for MinIO, install [a networking plugin that implements the Kubernetes NetworkPolicy spec](https://kubernetes.io/docs/tasks/administer-cluster/declare-network-policy#before-you-begin), and set `networkPolicy.enabled` to `true`. For Kubernetes v1.5 & v1.6, you must also turn on NetworkPolicy by setting the DefaultDeny namespace annotation. Note: this will enforce policy for *all* pods in the namespace:...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Oct 24 20:37:05 UTC 2022 - 20K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.28.md
- Sometimes, the scheduler incorrectly placed a pod in the "unschedulable" queue instead of the "backoff" queue. This happened when some plugin previously declared the pod as "unschedulable" and then in a later attempt encounters some other error. Scheduling of that pod then got delayed by up to five minutes, after which periodic flushing moved the pod back into the "active" queue. ([#120334](https://githu...
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Wed Oct 23 04:34:59 UTC 2024 - 456.9K bytes - Viewed (0)