Skip to content

Conversation

@hardcoretime
Copy link
Contributor

Description

Cloud-init userdata in the virtual machine specification should not be empty or exceed 2048 KB.

Why do we need it, and what problem does it solve?

These changes are required to prevent the virtual machine from entering a pending status due to incorrect cloud-init userdata.

What is the expected result?

Webhook prevents virtual machine creation or update with incorrect cloud-init userdata and Provisioning Handler return an error if resource was created with invalidated data.

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: feature
summary: "Cloud-init userdata is now validated during virtual machine creation and updates."

@hardcoretime hardcoretime added this to the v1.5.0 milestone Jan 29, 2026
@hardcoretime hardcoretime changed the title feat(vm): validate cloud init userdata feat(vm): validate cloud-init userdata Jan 29, 2026
Signed-off-by: Roman Sysoev <roman.sysoev@flant.com>
@hardcoretime hardcoretime force-pushed the feat/vm/validate-cloud-init-userdata branch from d5074c3 to 150f8a7 Compare January 29, 2026 23:41
@hardcoretime hardcoretime added the e2e/run Run e2e test on cluster of PR author label Jan 29, 2026
@deckhouse-BOaTswain
Copy link
Contributor

deckhouse-BOaTswain commented Jan 29, 2026

Workflow has started.
Follow the progress here: Workflow Run

The target step completed with status: failure.

@deckhouse-BOaTswain deckhouse-BOaTswain removed the e2e/run Run e2e test on cluster of PR author label Jan 30, 2026
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