[node-manager] handle k8s <1.20 in NG error events creation process #757
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Yuriy Losev yuriy.losev@flant.com
Description
Fix event creation for kubernetes <= 1.19
Why do we need it, and what problem does it solve?
events.k8s.io/v1
API was opened for publicity in k8 1.20, before it was available only for scheduler. K8s tries to convertevents.k8s.io/v1
tocore.io/v1
but it can't convert events that bind to ClusterScope resources properly.We can figure out a version of the k8s and create an event of the necessary type.
Changelog entries