fix(vms): actually apply inline userData + drop secretGenerator (amend 760084e)

760084e only committed the unifi-cloudinit.yaml deletion — the `git add` errored
on that already-staged pathspec and skipped the other two files, leaving the
kustomization still referencing the deleted file (broken build). Commit the
intended changes: 30-virtualmachine.yaml inline userData + kustomization.yaml
without the secretGenerator.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
This commit is contained in:
jakman85andClaude Opus 4.8 committed 2026-08-26 16:59:03 -05:00
1 parent 760084ea8c
commit ab592028f6
2 files changed
+27 -19

No files matched your search

-12
View File
@@ -11,15 +11,3 @@ resources:
- 30-virtualmachine.yaml
- 40-networkpolicy.yaml
- 50-service-l4.yaml
# The VM's cloud-init (SSH key + UOS install script) exceeds KubeVirt's 2048-byte inline userData
# limit, so it is delivered via a Secret (30-virtualmachine.yaml userDataSecretRef: unifi-cloudinit).
# secretGenerator wraps the readable unifi-cloudinit.yaml file as key `userdata`. disableNameSuffixHash
# keeps the name stable (the VM references it by fixed name — Kustomize can't rewrite a KubeVirt
# userDataSecretRef). Content is non-sensitive (public key + public installer), so NOT SOPS-encrypted.
secretGenerator:
- name: unifi-cloudinit
namespace: unifi
files:
- userdata=unifi-cloudinit.yaml
generatorOptions:
disableNameSuffixHash: true