status

Documentation

Index

• func IsDeleted(client client.Client, discovery discovery.CachedDiscoveryInterface, ...) (deleted bool, msg string, err error)
• func IsHealthy(obj runtime.Object) (healthy bool, msg string, err error)
• func IsReady(i kudoapi.Instance, c client.Client) (bool, string, error)
• func IsTerminallyFailed(obj runtime.Object) (terminal bool, msg string, err error)

Functions

func IsDeleted

func IsDeleted(client client.Client, discovery discovery.CachedDiscoveryInterface, obj runtime.Object) (deleted bool, msg string, err error)

IsTerminallyFailed returns true if a resource will never become healthy anymore and a corresponding message The returned msg is optional and should reflect the terminal state in a human readable form and potential reason. If the returned error is non-nil, the other returned values can be undefined and should not be used. This is a generic function and works on all resource types.

func IsHealthy

func IsHealthy(obj runtime.Object) (healthy bool, msg string, err error)

IsHealthy returns whether an object is healthy and a corresponding message. The message is optional and may be empty in any case; it is human readable and should reflect the returned healthy status and an optional reason. When the returned error is non-nil, all other parameters can have undefined values and should not be used. Must be implemented for each type; all unimplemented resources are considered healthy by default.

func IsReady

func IsReady(i kudoapi.Instance, c client.Client) (bool, string, error)

IsReady computes instance readiness based on current state of underlying resources currently readiness examines the following types: Pods, StatefulSets, Deployments, ReplicaSets and DaemonSets Instance is considered ready if all the resources linked to this instance are also ready (healthy)

func IsTerminallyFailed

func IsTerminallyFailed(obj runtime.Object) (terminal bool, msg string, err error)

IsTerminallyFailed returns true if a resource will never become healthy anymore and a corresponding message The returned msg is optional and should reflect the terminal state in a human readable form and may include a potential reason. If the returned error is non-nil, the other returned values can be undefined and should not be used. Must be implemented for each type; all unimplemented resources are considered non-terminal by default.