We should need an event return

[jjmengze]

Question

What did you do?

We can get the return of the event etc Create,Delete ...

What did you expect to see?

If we design an action here, we can know the state of the current resource.

type Request struct {
	// NamespacedName is the name and namespace of the object to reconcile.
	types.NamespacedName
}

What did you see instead? Under which circumstances?
By passing the action through the handler, the user can know the current resource situation.

// Create is called in response to an create event - e.g. Pod Creation.
func (h *NetHandler) Create(evt event.CreateEvent, q workqueue.RateLimitingInterface) {
	if evt.Meta == nil {
		fmt.Printf("evt.Meta == nil")
		return
	}

	q.Add(reconcile.Request{NamespacedName: types.NamespacedName{
		Name:      evt.Meta.GetName(),
		Namespace: evt.Meta.GetNamespace(),
		Action:    Create,
	}})
}

[j900155]

I have the same problem, @mengzn do you want to implement it?

[shawn-hurley]

Could you explain the use case and how you would use this field in your reconciler?

[jjmengze]

@shawn-hurley
It's still useful if the operator knows that an object has been deleted or modified!
The operator can handle his related business logic.

[shawn-hurley]

To handle the deletion, I believe that you should be using a finalizer.

Can you explain how you intend to use the modified data?

[jjmengze]

I think that it is not just a deletion.
If the operator can know the correction status of the object in the business. Help external operators understand changes in objects

[DirectXMan12]

You should never be writing reconcilers that differentiate between the different operations. That's bound to get you into trouble. Instead, each reconcile, you should check to see if the state of the world is different from what you expect, and act accordingly. It shouldn't matter if the object was just created or has been updated, what matters is that the state of the world conforms to what's specified in the object.

This request is explicitly against the design principles of controller-runtime, so I'm going to close it now. If I'm misunderstanding you, please let me know, and I'll re-open the issue.