Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 20 for scaling (0.17 sec)

  1. common-protos/k8s.io/api/autoscaling/v2beta2/generated.proto

      optional int32 periodSeconds = 3;
    }
    
    // HPAScalingRules configures the scaling behavior for one direction.
    // These Rules are applied after calculating DesiredReplicas from metrics for the HPA.
    // They can limit the scaling velocity by specifying scaling policies.
    // They can prevent flapping by specifying the stabilization window, so that the
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 21K bytes
    - Viewed (0)
  2. common-protos/k8s.io/api/autoscaling/v2beta1/generated.proto

      optional string container = 4;
    }
    
    // ContainerResourceMetricStatus indicates the current value of a resource metric known to
    // Kubernetes, as specified in requests and limits, describing a single container in each pod in the
    // current scale target (e.g. CPU or memory).  Such metrics are built in to
    // Kubernetes, and have special scaling options on top of those available to
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 21.2K bytes
    - Viewed (0)
  3. common-protos/k8s.io/api/apps/v1beta2/generated.proto

      // podManagementPolicy controls how pods are created during initial scale up,
      // when replacing pods on nodes, or when scaling down. The default policy is
      // `OrderedReady`, where pods are created in increasing order (pod-0, then
      // pod-1, etc) and the controller will wait until each pod is ready before
      // continuing. When scaling down, the pods are removed in the opposite order.
      // The alternative policy is `Parallel` which will create pods in parallel
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 36.4K bytes
    - Viewed (0)
  4. common-protos/k8s.io/api/autoscaling/v2/generated.proto

      optional int32 periodSeconds = 3;
    }
    
    // HPAScalingRules configures the scaling behavior for one direction.
    // These Rules are applied after calculating DesiredReplicas from metrics for the HPA.
    // They can limit the scaling velocity by specifying scaling policies.
    // They can prevent flapping by specifying the stabilization window, so that the
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 21.3K bytes
    - Viewed (0)
  5. common-protos/k8s.io/api/autoscaling/v1/generated.proto

      optional string container = 5;
    }
    
    // ContainerResourceMetricStatus indicates the current value of a resource metric known to
    // Kubernetes, as specified in requests and limits, describing a single container in each pod in the
    // current scale target (e.g. CPU or memory).  Such metrics are built in to
    // Kubernetes, and have special scaling options on top of those available to
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 22K bytes
    - Viewed (0)
  6. operator/README.md

    control plane components.
    - [Component configuration API](https://github.com/istio/api/blob/00671adacbea20f941cb20cce021bc63cbad1840/operator/v1alpha1/operator.proto#L42-L93), for managing
    K8s settings like resources, auto scaling, pod disruption budgets and others defined in the
    [KubernetesResourceSpec](https://github.com/istio/api/blob/00671adacbea20f941cb20cce021bc63cbad1840/operator/v1alpha1/operator.proto#L217-L271)
    for Istio core and addon components.
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sun Sep 17 08:27:52 GMT 2023
    - 17.5K bytes
    - Viewed (0)
  7. common-protos/k8s.io/api/apps/v1/generated.proto

      // podManagementPolicy controls how pods are created during initial scale up,
      // when replacing pods on nodes, or when scaling down. The default policy is
      // `OrderedReady`, where pods are created in increasing order (pod-0, then
      // pod-1, etc) and the controller will wait until each pod is ready before
      // continuing. When scaling down, the pods are removed in the opposite order.
      // The alternative policy is `Parallel` which will create pods in parallel
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 34.5K bytes
    - Viewed (0)
  8. common-protos/k8s.io/api/apps/v1beta1/generated.proto

      // podManagementPolicy controls how pods are created during initial scale up,
      // when replacing pods on nodes, or when scaling down. The default policy is
      // `OrderedReady`, where pods are created in increasing order (pod-0, then
      // pod-1, etc) and the controller will wait until each pod is ready before
      // continuing. When scaling down, the pods are removed in the opposite order.
      // The alternative policy is `Parallel` which will create pods in parallel
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24K bytes
    - Viewed (0)
  9. common-protos/k8s.io/api/extensions/v1beta1/generated.proto

      // Example: when this is set to 30%, the old RC can be scaled down to 70% of desired pods
      // immediately when the rolling update starts. Once new pods are ready, old RC
      // can be scaled down further, followed by scaling up the new RC, ensuring
      // that the total number of pods available at all times during the update is at
      // least 70% of desired pods.
      // +optional
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 45.6K bytes
    - Viewed (0)
  10. manifests/charts/istio-control/istio-discovery/values.yaml

          excludeInboundPorts: ""
          includeInboundPorts: "*"
    
          # istio egress capture allowlist
          # https://istio.io/docs/tasks/traffic-management/egress.html#calling-external-services-directly
          # example: includeIPRanges: "172.30.0.0/16,172.20.0.0/16"
          # would only capture egress traffic on those two IP Ranges, all other outbound traffic would
          # be allowed by the sidecar
    Others
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Apr 22 22:00:40 GMT 2024
    - 20.3K bytes
    - Viewed (0)
Back to top