draincontroller

Documentation

Index

• Constants
• type Controller
  • func NewController(controllerName string, kubeclientset kubernetes.Interface, ...) *Controller
  • func (c *Controller) AddInstance(instance *brokerv1beta1.ActiveMQArtemisScaledown)
  • func (c *Controller) GetStopCh() *chan struct{}
  • func (c *Controller) Run(threadiness int) error

Constants

const (
	SuccessCreate    = "SuccessfulCreate"
	DrainSuccess     = "DrainSuccess"
	PVCDeleteSuccess = "SuccessfulPVCDelete"
	PodDeleteSuccess = "SuccessfulDelete"

	MessageDrainPodCreated  = "create Drain Pod %s in StatefulSet %s successful"
	MessageDrainPodFinished = "drain Pod %s in StatefulSet %s completed successfully"
	MessageDrainPodDeleted  = "delete Drain Pod %s in StatefulSet %s successful"
	MessagePVCDeleted       = "delete Claim %s in StatefulSet %s successful"
)

const AnnotationDrainerPodTemplate = "statefulsets.kubernetes.io/drainer-pod-template"

const AnnotationStatefulSet = "statefulsets.kubernetes.io/drainer-pod-owner" // TODO: can we replace this with an OwnerReference with the StatefulSet as the owner?

const DrainRoleName = "drain-pod-role"

const DrainServiceAccountName = "drain-pod-service-account"

const LabelDrainPod = "drain-pod"

Types

type Controller

type Controller struct {
	// contains filtered or unexported fields
}

func NewController

func NewController(

	controllerName string,
	kubeclientset kubernetes.Interface,
	kubeInformerFactory kubeinformers.SharedInformerFactory,
	namespace string,
	client client.Client,
	instance *brokerv1beta1.ActiveMQArtemisScaledown,
	logger logr.Logger) *Controller

NewController returns a new sample controller

func (*Controller) AddInstance

func (c *Controller) AddInstance(instance *brokerv1beta1.ActiveMQArtemisScaledown)

func (*Controller) GetStopCh

func (c *Controller) GetStopCh() *chan struct{}

func (*Controller) Run

func (c *Controller) Run(threadiness int) error

Run will set up the event handlers for types we are interested in, as well as syncing informer caches and starting workers. It will block until stopCh is closed, at which point it will shutdown the workqueue and wait for workers to finish processing their current work items.