fix(vm): watch to provisioning secrets #1820
Merged
+113
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Valeriy Khorunzhin <[email protected]>
Signed-off-by: Valeriy Khorunzhin <[email protected]>
Contributor
|
Workflow has started. |
Isteb4k
approved these changes
Dec 12, 2025
Isteb4k
pushed a commit
that referenced
this pull request
Dec 15, 2025
Signed-off-by: Valeriy Khorunzhin <[email protected]> (cherry picked from commit e20f167)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
React to creating and modifying provisioning secrets.
Why do we need it, and what problem does it solve?
If a VM refers to a provisioning secret and is created before it exists, it may remain pending because there is no reason to reconcile.
What is the expected result?
A VM starts.
Checklist
Changelog entries