Documentation ¶
Overview ¶
Package liqonodeprovider implements the VirtualKubelet NodeProvider interface, it manages the node status monitoring the status of the Liqo resources (i.e. TunnelEndpoints, Advertisements and ResourceOffers)
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func UnknownNodeConditions ¶
func UnknownNodeConditions() []corev1.NodeCondition
UnknownNodeConditions returns an array of node conditions with all unknown status.
func UpdateNodeCondition ¶
func UpdateNodeCondition(node *corev1.Node, conditionType corev1.NodeConditionType, conditionStatus func() (corev1.ConditionStatus, string, string))
UpdateNodeCondition updates the specified node condition, depending on the outcome of the specified function.
Types ¶
type LiqoNodeProvider ¶
type LiqoNodeProvider struct {
// contains filtered or unexported fields
}
LiqoNodeProvider is a node provider that manages the Liqo resources.
func NewLiqoNodeProvider ¶
func NewLiqoNodeProvider( nodeName, foreignClusterID, kubeletNamespace string, node *v1.Node, podProviderStopper, networkReadyChan chan struct{}, config *rest.Config, resyncPeriod time.Duration) (*LiqoNodeProvider, error)
NewLiqoNodeProvider creates and returns a new LiqoNodeProvider.
func (*LiqoNodeProvider) IsTerminating ¶
func (p *LiqoNodeProvider) IsTerminating() bool
IsTerminating indicates if the node is in terminating (and in the draining phase).
func (*LiqoNodeProvider) NotifyNodeStatus ¶
func (p *LiqoNodeProvider) NotifyNodeStatus(ctx context.Context, f func(*corev1.Node))
NotifyNodeStatus implements the NodeProvider interface.
func (*LiqoNodeProvider) Ping ¶
func (p *LiqoNodeProvider) Ping(ctx context.Context) error
Ping just implements the NodeProvider interface. It returns the error from the passed in context only.
func (*LiqoNodeProvider) StartProvider ¶
func (p *LiqoNodeProvider) StartProvider() (ready, stop chan struct{})
StartProvider starts the provider with its infromers on Liqo resources. These informers on sharing and network resources will be used to accordingly update the virtual node.