smee
smee copied to clipboard
Introduction of report for k8s client
Description
Why is this needed
Currently the k8s reporter is not implemented, as a result among other things the DisablePXE method is a no-op.
As a result in scenarios when leveraging custom-pxe, no DisablePXE is performed.
The PR introduces a reporter implementation of the k8s client. This allows the implementation for DisablePXE implementatino.
In addition, the OSIE / boots events are now also logged as k8s events associated with the hardware objects.
Fixes: #
How Has This Been Tested?
A simple unit test leveraging envTest is available which can simulate the events and hardware updates.
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have:
- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade