Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 7 of 7 for disruptors (0.43 sec)

  1. common-protos/k8s.io/api/policy/v1/generated.proto

      //               the number of allowed disruptions. Therefore no disruptions are
      //               allowed and the status of the condition will be False.
      // - InsufficientPods: The number of pods are either at or below the number
      //                     required by the PodDisruptionBudget. No disruptions are
      //                     allowed and the status of the condition will be False.
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 8K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/policy/v1beta1/generated.proto

      //               the number of allowed disruptions. Therefore no disruptions are
      //               allowed and the status of the condition will be False.
      // - InsufficientPods: The number of pods are either at or below the number
      //                     required by the PodDisruptionBudget. No disruptions are
      //                     allowed and the status of the condition will be False.
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 19.6K bytes
    - Viewed (0)
  3. helm/minio/values.yaml

      flavor: kubernetes
      allowExternal: true
      # only when using flavor: cilium
      egressEntities:
       - kube-apiserver
    
    ## PodDisruptionBudget settings
    ## ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/
    ##
    podDisruptionBudget:
      enabled: false
      maxUnavailable: 1
    
    ## Specify the service account to use for the MinIO pods. If 'create' is set to 'false'
    Others
    - Registered: Sun Apr 28 19:28:10 GMT 2024
    - Last Modified: Sun Apr 28 10:14:37 GMT 2024
    - 18.4K bytes
    - Viewed (0)
  4. docs/en/docs/deployment/concepts.md

    * Memory
    * Previous steps before starting
    
    We'll see how they would affect **deployments**.
    
    In the end, the ultimate objective is to be able to **serve your API clients** in a way that is **secure**, to **avoid disruptions**, and to use the **compute resources** (for example remote servers/virtual machines) as efficiently as possible. 🚀
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Thu May 02 22:37:31 GMT 2024
    - 18K bytes
    - Viewed (0)
  5. helm-releases/minio-5.2.0.tgz

    kubernetes) # or Cilium Network Policies (flavor: cilium) flavor: kubernetes allowExternal: true # only when using flavor: cilium egressEntities: - kube-apiserver ## PodDisruptionBudget settings ## ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/ ## podDisruptionBudget: enabled: false maxUnavailable: 1 ## Specify the service account to use for the MinIO pods. If 'create' is set to 'false' ## and 'name' is left unspecified, the account 'default' will be used. serviceAccount: create: true...
    Others
    - Registered: Sun Apr 28 19:28:10 GMT 2024
    - Last Modified: Sun Apr 28 10:14:37 GMT 2024
    - 21.7K bytes
    - Viewed (0)
  6. helm-releases/minio-5.0.15.tgz

    redirectUri: "https://console-endpoint-url/oauth_callback" # Can leave empty claimPrefix: "" comment: "" networkPolicy: enabled: false allowExternal: true ## PodDisruptionBudget settings ## ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/ ## podDisruptionBudget: enabled: false maxUnavailable: 1 ## Specify the service account to use for the MinIO pods. If 'create' is set to 'false' ## and 'name' is left unspecified, the account 'default' will be used. serviceAccount: create: true...
    Others
    - Registered: Sun Apr 28 19:28:10 GMT 2024
    - Last Modified: Fri Jan 12 18:18:57 GMT 2024
    - 20.8K bytes
    - Viewed (0)
  7. helm-releases/minio-5.1.0.tgz

    kubernetes) # or Cilium Network Policies (flavor: cilium) flavor: kubernetes allowExternal: true # only when using flavor: cilium egressEntities: - kube-apiserver ## PodDisruptionBudget settings ## ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/ ## podDisruptionBudget: enabled: false maxUnavailable: 1 ## Specify the service account to use for the MinIO pods. If 'create' is set to 'false' ## and 'name' is left unspecified, the account 'default' will be used. serviceAccount: create: true...
    Others
    - Registered: Sun Apr 28 19:28:10 GMT 2024
    - Last Modified: Sun Mar 03 18:49:37 GMT 2024
    - 21.3K bytes
    - Viewed (0)
Back to top