Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for MinDomainsInPodTopologySpread (0.68 sec)

  1. CHANGELOG/CHANGELOG-1.30.md

    - Graduated support for `minDomains` in pod topology spread constraints, to general availability.
      The `MinDomainsInPodTopologySpread` feature gate no longer has any effect, and the field is
      always available within the Pod and PodTemplate APIs. ([#123481](https://github.com/kubernetes/kubernetes/pull/123481), [@sanposhiho](https://github.com/sanposhiho))
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed Jun 12 04:05:28 UTC 2024
    - 253.2K bytes
    - Viewed (0)
  2. CHANGELOG/CHANGELOG-1.27.md

    - `MinDomainsInPodTopologySpread` feature gate is enabled by default as a
      Beta feature in 1.27. ([#114445](https://github.com/kubernetes/kubernetes/pull/114445), [@mengjiao-liu](https://github.com/mengjiao-liu))
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Tue Jun 11 23:01:06 UTC 2024
    - 455.3K bytes
    - Viewed (0)
  3. common-protos/k8s.io/api/core/v1/generated.proto

      // because computed skew will be 3(3 - 0) if new Pod is scheduled to any of the three zones,
      // it will violate MaxSkew.
      //
      // This is a beta field and requires the MinDomainsInPodTopologySpread feature gate to be enabled (enabled by default).
      // +optional
      optional int32 minDomains = 5;
    
      // NodeAffinityPolicy indicates how we will treat Pod's nodeAffinity/nodeSelector
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Mon Mar 11 18:43:24 UTC 2024
    - 255.8K bytes
    - Viewed (0)
Back to top