You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
We need the ability to specify node pools independently from the cluster resource itself. We have automations that add and remove node pools entirely depending on failover scenarios. Currently with a secondary pool configured inside the linode_lke_cluster resource, you cannot specify the pool have a count=0 or autoscalermin = 0. Unless there's some other trick i'm not thinking of, this means I cannot easily add and remove pools based on a simple variable. (I would have to update my code to comment out the pool). What i'm asking for is akin to digital oceans's kubernetes_node_pool.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature Request:
We need the ability to specify node pools independently from the cluster resource itself. We have automations that add and remove node pools entirely depending on failover scenarios. Currently with a secondary pool configured inside the linode_lke_cluster resource, you cannot specify the pool have a
count
=0
orautoscaler
min
=0
. Unless there's some other trick i'm not thinking of, this means I cannot easily add and remove pools based on a simple variable. (I would have to update my code to comment out the pool). What i'm asking for is akin to digital oceans's kubernetes_node_pool.The text was updated successfully, but these errors were encountered: