Placement group contains already 10 servers #641
-
I was trying to add a new node agent pool, but Terraform is showing me the following error.
For placement group config placement_group_disable it says:
As I have much fewer nodes I was not expecting any problems. Do I have to enable this flag as soon as I have more than 10 nodes in the cluster? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 10 replies
-
@jonas-tm Just comment out this flag, or set it explicitly to false, and it will automatically handle as many servers as you need. |
Beta Was this translation helpful? Give feedback.
-
@jonas-tm Issues have been fixed in the newly released v1.10.4. By default placement group is enabled and you can have up to 500 nodes. If you disable it, you loose the physical spread of the machines but can deploy even more machines. In both cases it will work now! 🚀 |
Beta Was this translation helpful? Give feedback.
-
release v1.10.4 for now this throws an error if there are 10 (20, 30, ...) nodes in agent_nodes terraform: for this: and this:
fix:
|
Beta Was this translation helpful? Give feedback.
release v1.10.4
for now this throws an error if there are 10 (20, 30, ...) nodes in agent_nodes
terraform:
The given key does not identify an element in this collection value: the given index is greater than or equal to the length of the collection.
for this:
hcloud_placement_group.agent[floor((index(keys(local.agent_nodes), each.key) + 1) / 10)].id
and this:
hcloud_placement_group.control_plane[floor((index(keys(local.control_plane_nodes), each.key) + 1) / 10)].id
floor((10 + 1) / 10) = 1
fix:
hcloud_placement_group.agent[floor((index(keys(local.agent_nodes), each.key)) / 10)].id
hcloud_placement_group.control_plane[floor((index(keys(local.control_plane_nodes), each.key)) / 10)].id
floor…