Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[node-manager] handle k8s <1.20 in NG error events creation process #757

Merged
merged 1 commit into from
Feb 3, 2022

Conversation

yalosev
Copy link
Member

@yalosev yalosev commented Feb 2, 2022

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 convert events.k8s.io/v1 to core.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

module: node-manager
type: fix
description: Fix event creation for NG when new Machine provisioning process is failed

@yalosev yalosev added the status/backport Backport pr label Feb 2, 2022
@yalosev yalosev self-assigned this Feb 2, 2022
@yalosev
Copy link
Member Author

yalosev commented Feb 2, 2022

@z9r5 have to backport in 1.30

Signed-off-by: Yuriy Losev <yuriy.losev@flant.com>
@nabokihms nabokihms added this to the v1.30.9 milestone Feb 3, 2022
@nabokihms nabokihms merged commit 46eee57 into main Feb 3, 2022
@nabokihms nabokihms deleted the fix-ng-event-creation branch February 3, 2022 13:37
@z9r5
Copy link
Member

z9r5 commented Feb 9, 2022

Cherry-picked into release-1.30

@z9r5 z9r5 removed the status/backport Backport pr label Feb 9, 2022
z9r5 pushed a commit that referenced this pull request Feb 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants