Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for AddEventHandler (0.09 sec)

  1. cni/pkg/nodeagent/informers.go

    		controllers.WithMaxAttempts(5),
    	)
    	// We only need to handle pods on our node
    	s.pods = kclient.NewFiltered[*corev1.Pod](kubeClient, kclient.Filter{FieldSelector: "spec.nodeName=" + NodeName})
    	s.pods.AddEventHandler(controllers.FromEventHandler(func(o controllers.Event) {
    		s.queue.Add(o)
    	}))
    
    	// Namespaces could be anything though, so we watch all of those
    	//
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Wed Oct 09 16:05:45 UTC 2024
    - 11.7K bytes
    - Viewed (0)
  2. architecture/networking/controllers.md

    Construction should create informers (via `kclient.New`), setup a queue (via `controllers.NewQueue`), and register event handlers on the informers.
    Often, these handlers are adding something to the queue like `client.AddEventHandler(controllers.ObjectHandler(queue.AddObject))`.
    Construction should NOT actually start running all of these things, do I/O, or block in anyway.
    
    Running the controller actually starts processing things.
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Fri Feb 09 17:41:25 UTC 2024
    - 4.9K bytes
    - Viewed (0)
  3. cni/pkg/repair/repaircontroller.go

    		FieldSelector: strings.Join(fieldSelectors, ","),
    	})
    	c.queue = controllers.NewQueue("repair pods",
    		controllers.WithReconciler(c.Reconcile),
    		controllers.WithMaxAttempts(5))
    	c.pods.AddEventHandler(controllers.ObjectHandler(c.queue.AddObject))
    
    	return c, nil
    }
    
    func (c *Controller) Run(stop <-chan struct{}) {
    	kube.WaitForCacheSync("repair controller", stop, c.pods.HasSynced)
    	c.queue.Run(stop)
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Feb 10 00:31:55 UTC 2024
    - 10.4K bytes
    - Viewed (0)
Back to top