Documentation
¶
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type AffinityTerm ¶ added in v1.19.0
type AffinityTerm = framework.AffinityTerm
AffinityTerm is a processed version of v1.PodAffinityTerm.
type HostPortInfo ¶ added in v1.19.0
type HostPortInfo = framework.HostPortInfo
HostPortInfo stores mapping from ip to a set of ProtocolPort
type ImageStateSummary ¶ added in v1.19.0
type ImageStateSummary = framework.ImageStateSummary
ImageStateSummary provides summarized information about the state of an image.
type NodeInfo ¶ added in v1.19.0
NodeInfo is node level aggregated information.
func NewNodeInfo ¶ added in v1.19.0
NewNodeInfo returns a ready to use empty NodeInfo object. If any pods are given in arguments, their information will be aggregated in the returned object.
type PodInfo ¶
PodInfo is a wrapper to a Pod with additional pre-computed information to accelerate processing. This information is typically immutable (e.g., pre-processed inter-pod affinity selectors).
func NewPodInfo ¶ added in v1.19.0
NewPodInfo return a new PodInfo
type ProtocolPort ¶ added in v1.19.0
type ProtocolPort = framework.ProtocolPort
ProtocolPort represents a protocol port pair, e.g. tcp:80.
type QueuedPodInfo ¶ added in v1.19.0
type QueuedPodInfo = framework.QueuedPodInfo
QueuedPodInfo is a Pod wrapper with additional information related to the pod's status in the scheduling queue, such as the timestamp when it's added to the queue.
type Resource ¶ added in v1.19.0
Resource is a collection of compute resource.
func NewResource ¶ added in v1.19.0
func NewResource(rl v1.ResourceList) *Resource
NewResource creates a Resource from ResourceList
type TransientSchedulerInfo ¶ added in v1.19.0
type TransientSchedulerInfo = framework.TransientSchedulerInfo
TransientSchedulerInfo is a transient structure which is destructed at the end of each scheduling cycle. It consists of items that are valid for a scheduling cycle and is used for message passing across predicates and priorities. Some examples which could be used as fields are number of volumes being used on node, current utilization on node etc. IMPORTANT NOTE: Make sure that each field in this structure is documented along with usage. Expand this structure only when absolutely needed as this data structure will be created and destroyed during every scheduling cycle.
type WeightedAffinityTerm ¶ added in v1.19.0
type WeightedAffinityTerm = framework.WeightedAffinityTerm
WeightedAffinityTerm is a "processed" representation of v1.WeightedAffinityTerm.