Task to fire Kubernetes events
What does this MR do?
This change introduces a simple Task
to declare and fire a
Kubernetes Event. It uses EventRecorder
interface from client-go
.
But this interface uses core/v1
Event type and not the new Events
API, events.k8s.io/v1
.
The Event task is fire and forget and does not run any follow-up check to ensure that the Event is raised by the API.
In addition to the source object, which in most cases is a GitLab
custom resource, the core Event has Type
(either Normal
or
Warning
), Reason
, and Message
.
Author's Checklist
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
-
Ensure a release milestone is set. -
MR title and description are up to date, accurate, and descriptive. -
MR targeting the appropriate branch. -
MR has a green pipeline on GitLab.com. -
When ready for review, MR is labeled workflowready for review per the MR workflow.
Expected
-
Test plan indicating conditions for success has been posted and passes. -
Documentation is created or updated. -
Tests are added.
Related issues
Closes #40 (closed)
Edited by Hossein Pursultani