scheduler

Documentation

Index

• Constants
• type Controller
  • func New(ctx *controllerpkg.Context) *Controller
  • func (c *Controller) Run(workers int, stopCh <-chan struct{}) error
  • func (c *Controller) Sync(ctx context.Context, ch *cmapi.Challenge) error

Constants

const (
	ControllerName = "challenges-scheduler"
)

Types

type Controller

type Controller struct {
	controllerpkg.Context
	// contains filtered or unexported fields
}

func New

func New(ctx *controllerpkg.Context) *Controller

func (*Controller) Run

func (c *Controller) Run(workers int, stopCh <-chan struct{}) error

func (*Controller) Sync

func (c *Controller) Sync(ctx context.Context, ch *cmapi.Challenge) error

Sync will process a single ACME challenge resource in order to determine whether it can be scheduled for processing. This is currently extremelly primitive, and **will not** do intelligent things like bumping challenges that are for already expired or nearing expiry certificates to the 'front' of the queue.

This may be something to do in future - we could use a resyncFunc to build a stack of challenges to process, and upon observation of a new challenge, re-evaluate the whole stack.

For now, this function will simply be used to solve https://github.com/jetstack/cert-manager/issues/951