Damien Grisonnet d00364902b events: fix EventSeries starting count discrepancy ... The kube-apiserver validation expects the Count of an EventSeries to be at least 2, otherwise it rejects the Event. There was is discrepancy between the client and the server since the client was iniatizing an EventSeries to a count of 1. According to the original KEP, the first event emitted should have an EventSeries set to nil and the second isomorphic event should have an EventSeries with a count of 2. Thus, we should matcht the behavior define by the KEP and update the client. Also, as an effort to make the old clients compatible with the servers, we should allow Events with an EventSeries count of 1 to prevent any unexpected rejections. Signed-off-by: Damien Grisonnet <dgrisonn@redhat.com>		2023-03-13 13:31:07 +01:00
..
events_test.go	events: fix EventSeries starting count discrepancy	2023-03-13 13:31:07 +01:00
main_test.go