Optional Map of node name to % of traffic to send to it FieldĪpply egreedy algorithm with given epsilon value If no fields then the default is to send traffic to all children nodes. Object must adhere to KNative Addressable pattern. Reference to an object that will be used to find target endpoint. Reference to existing kubernetes resource The name of the container in the inline spec that implements this node A DAGSpec with no implementation is assumed to have a container in the custom spec with the same name.Default is to pass traffic as it arrives. Optional spec for merging traffic from dependencies. Default is to send all traffic to all children nodes (optional) Optional spec for routing traffic to forward nodes.
The implementation for this node (optional)
(optional)Ī list of DAG names that this node depends on. FieldĪ list of inline specs for implementing the nodes. All fields are mutable and may be applied idempotently. This infrastructure-as-code paradigm enables the coveted GitOps design pattern, where configurations are checked into git and may be reverted and applied to restore previous configurations. Changes made to the spec will be enacted upon the underlying servers in an eventually consistent manner. The Spec section of the resource definition encapsulates the desired state of the user's model serving resources. This top level resource definition is shared by all Kubernetes Custom Resources. An MLGraph joins together various atomic ML components into a graph.
0 kommentar(er)
