Skip to content

Allow unsetting runtimeClassName#1625

Closed
sklirg wants to merge 1 commit into
NVIDIA:mainfrom
sklirg:fix/runtimeclassname-allow-unsetting
Closed

Allow unsetting runtimeClassName#1625
sklirg wants to merge 1 commit into
NVIDIA:mainfrom
sklirg:fix/runtimeclassname-allow-unsetting

Conversation

@sklirg
Copy link
Copy Markdown

@sklirg sklirg commented Feb 19, 2026

Default value to nil in case it is unset.
If the value previously has been set, but is now unset, the conditional branch would remove the field from the generated manifest, resulting in a manifest merge to retain the field as it was not specified to be removed/nulled.

Default value to nil in case it is unset.
If the value previously has been set, but is now unset,
the conditional branch would remove the field from the generated manifest,
resulting in a manifest merge to retain the field as it was not
specified to be removed/nulled.

Signed-off-by: Håkon Solbjørg <hakon@solbj.org>
@copy-pr-bot
Copy link
Copy Markdown

copy-pr-bot Bot commented Feb 19, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@rajatchopra
Copy link
Copy Markdown
Contributor

Not sure if this is the right solution.
| default nil will result in rendering runtimeClassName: <nil> which isn't valid.

Closing this PR. Please re-open if anyone thinks it is still the right path.

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.

2 participants