Related to T4618
Details
Details
- Reviewers
olasd - Group Reviewers
System administrators - Maniphest Tasks
- T4618: Migrate large workers (worker17-18) to elastic workers
- Commits
- rSPRE9176a602ee0c: production-worker05: Increase memory and scratch disk space
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: ~ update in-place Terraform will perform the following actions: # module.rancher-node-production-worker05.proxmox_vm_qemu.node will be updated in-place ~ resource "proxmox_vm_qemu" "node" { ~ balloon = 16384 -> 32768 id = "uffizi/qemu/112" ~ memory = 32768 -> 65536 name = "rancher-node-production-worker05" # (37 unchanged attributes hidden) ~ disk { ~ size = "30G" -> "50G" # (17 unchanged attributes hidden) } # (2 unchanged blocks hidden) } Plan: 0 to add, 1 to change, 0 to destroy.
Diff Detail
Diff Detail
- Repository
- rSPRE sysadm-provisioning
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Comment Actions
does ballooning interact correctly with kubernetes' memory accounting? I assume that'd do a better job if the node only had a static amount of memory.