Skip to content

Conversation

@eofff
Copy link
Contributor

@eofff eofff commented Dec 12, 2025

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

  • The code is covered by unit tests.
  • e2e tests passed.
  • Documentation updated according to the changes.
  • Changes were tested in the Kubernetes cluster manually.

Changelog entries

section: vm
type: fix
summary: React to creating and modifying provisioning secrets.
impact_level: low

Signed-off-by: Valeriy Khorunzhin <[email protected]>
@eofff eofff added this to the v1.4.0 milestone Dec 12, 2025
@eofff eofff merged commit 82564c2 into release-1.0-cse Dec 12, 2025
27 of 29 checks passed
@eofff eofff deleted the fix/vm/cse-watch-for-secrets branch December 12, 2025 12:13
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.

3 participants