7 Commits

Author	SHA1	Message	Date
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
Wojciech Tyczyński	2af8d0bbd7	Clean shutdown of events integration tests	2022-06-06 20:33:20 +02:00
Wojciech Tyczyński	551790729f	Remove selflink references in different testing-related files	2022-01-14 12:58:05 +01:00
Chelsey Chen	ade2422883	Switch event recorder to use events.k8s.io/v1	2020-07-02 14:50:41 -04:00
Mike Danese	3aa59f7f30	generated: run refactor	2020-02-07 18:16:47 -08:00
wojtekt	bc00248e71	Fix selflinks in tests	2019-08-01 15:50:03 +02:00
Yassine TIJANI	bfa12a0992	add integration test for core/v1beta1 event compatibility ... Signed-off-by: Yassine TIJANI <ytijani@vmware.com>	2019-05-30 15:01:15 +00:00