Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 10 for scalar (0.23 sec)

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

    // Package-wide variables from generator "generated".
    option go_package = "k8s.io/api/autoscaling/v2beta2";
    
    // ContainerResourceMetricSource indicates how to scale on a resource metric known to
    // Kubernetes, as specified in requests and limits, describing each pod in the
    // current scale target (e.g. CPU or memory).  The values will be averaged
    // together before being compared to the target.  Such metrics are built in to
    Plain Text
    - Registered: Wed Apr 24 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

    // Package-wide variables from generator "generated".
    option go_package = "k8s.io/api/autoscaling/v2beta1";
    
    // ContainerResourceMetricSource indicates how to scale on a resource metric known to
    // Kubernetes, as specified in requests and limits, describing each pod in the
    // current scale target (e.g. CPU or memory).  The values will be averaged
    // together before being compared to the target.  Such metrics are built in to
    Plain Text
    - Registered: Wed Apr 24 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

      optional ScaleSpec spec = 2;
    
      // current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only.
      // +optional
      optional ScaleStatus status = 3;
    }
    
    // ScaleSpec describes the attributes of a scale subresource
    message ScaleSpec {
      // desired number of instances for the scaled object.
      // +optional
      optional int32 replicas = 1;
    }
    Plain Text
    - Registered: Wed Apr 24 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/v1/generated.proto

    message HorizontalPodAutoscalerSpec {
      // reference to scaled resource; horizontal pod autoscaler will learn the current resource consumption
      // and will set the desired number of pods by using its Scale subresource.
      optional CrossVersionObjectReference scaleTargetRef = 1;
    
      // minReplicas is the lower limit for the number of replicas to which the autoscaler
      // can scale down.  It defaults to 1 pod.  minReplicas is allowed to be 0 if the
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 22K bytes
    - Viewed (0)
  5. common-protos/k8s.io/api/apps/v1beta1/generated.proto

      // status defines current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only.
      // +optional
      optional ScaleStatus status = 3;
    }
    
    // ScaleSpec describes the attributes of a scale subresource
    message ScaleSpec {
      // replicas is the number of observed instances of the scaled object.
      // +optional
      optional int32 replicas = 1;
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 24K bytes
    - Viewed (0)
  6. architecture/ambient/ztunnel.md

      * Specifically, ztunnel should be able to send a request to the control plane to answer "I got a request to send traffic to 1.1.1.1, what is 1.1.1.1?"
      * While this is not needed for small scales, this is important for the long tail of massive clusters (think 1 million endpoints), where the entire set of endpoints cannot reasonably be replicated to each ztunnel.
    * It should not be client-specific.
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Wed Sep 13 02:17:30 GMT 2023
    - 16.6K bytes
    - Viewed (0)
  7. common-protos/k8s.io/api/autoscaling/v2/generated.proto

    // Package-wide variables from generator "generated".
    option go_package = "k8s.io/api/autoscaling/v2";
    
    // ContainerResourceMetricSource indicates how to scale on a resource metric known to
    // Kubernetes, as specified in requests and limits, describing each pod in the
    // current scale target (e.g. CPU or memory).  The values will be averaged
    // together before being compared to the target.  Such metrics are built in to
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 21.3K bytes
    - Viewed (0)
  8. common-protos/k8s.io/api/apps/v1/generated.proto

      // This can not be 0 if MaxSurge is 0.
      // Defaults to 25%.
      // Example: when this is set to 30%, the old ReplicaSet can be scaled down to 70% of desired pods
      // immediately when the rolling update starts. Once new pods are ready, old ReplicaSet
      // can be scaled down further, followed by scaling up the new ReplicaSet, ensuring
      // that the total number of pods available at all times during the update is at
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 34.5K bytes
    - Viewed (0)
  9. common-protos/k8s.io/api/extensions/v1beta1/generated.proto

      optional ScaleSpec spec = 2;
    
      // current status of the scale. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. Read-only.
      // +optional
      optional ScaleStatus status = 3;
    }
    
    // describes the attributes of a scale subresource
    message ScaleSpec {
      // desired number of instances for the scaled object.
      // +optional
      optional int32 replicas = 1;
    }
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 45.6K bytes
    - Viewed (0)
  10. architecture/networking/pilot.md

    #### Optimizations
    
    A naive implementation would simply regenerate all resources, of all subscribed types, for each client, on any configuration change. However, this scales poorly. As a result, we have many levels of optimizations to avoid doing this work.
    
    Plain Text
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Wed Feb 07 17:53:24 GMT 2024
    - 19.1K bytes
    - Viewed (0)
Back to top