-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for spot node pool in azurerm_kubernetes_cluster #6086
Comments
- Support for spot node pool in azurerm_kubernetes_cluster Fixes hashicorp#6086
I've raise a PR for this above. I tried but this isn't working for me. Must be missing something simple.
Point me to changes and I would love to get this done urgently. Thanks. |
- Support for spot node pool in azurerm_kubernetes_cluster Fixes #6086
hey, i'd really like to get this moving, anything I can do to help push this? |
* Support of Spot Priority for `azurerm_kubernetes_cluster_node_pool` * `node_taints` and `node_labels` were marked as computed and they must force a pool recreation. The initial work was started as hashicorp#6231 Fixes hashicorp#6086 Co-Authored-By: Alok Kumar <[email protected]>
* Support of Spot Priority for `azurerm_kubernetes_cluster_node_pool` * `node_taints` and `node_labels` were marked as computed and they must force a pool recreation. The initial work was started as hashicorp#6231 Fixes hashicorp#6086 Co-Authored-By: Alok Kumar <[email protected]>
* Support of Spot Priority for `azurerm_kubernetes_cluster_node_pool` * `node_taints` and `node_labels` were marked as *computed* and they must force a pool recreation. The initial work was started as hashicorp#6231 Fixes hashicorp#6086 Co-Authored-By: Alok Kumar <[email protected]>
@4c74356b41 Please have a look at #7145. |
* Support of Spot Priority for `azurerm_kubernetes_cluster_node_pool` * `node_taints` and `node_labels` were marked as *computed* and they must force a pool recreation. The initial work was started as hashicorp#6231 Fixes hashicorp#6086 Co-Authored-By: Alok Kumar <[email protected]>
I'm afraid I dont really know how terraform is working, so its hard for me to be of value, but I can test the result, or, perhaps, if you need some help on the azure side, I could do that |
* Support of Spot Priority for `azurerm_kubernetes_cluster_node_pool` * `node_taints` and `node_labels` were marked as *computed* and they must force a new pool resource * Add `max_bid_price` validation for `windows_virtual_machine_scale_set` and `linux_virtual_machine_scale_set` The initial work was started as hashicorp#6231 Fixes hashicorp#6086 Co-Authored-By: Alok Kumar <[email protected]>
This has been released in version 2.14.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.14.0"
}
# ... other configuration ... |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Community Note
Request to support for spot node pool in azurerm_kubernetes_cluster
Request to support for spot node pool in azurerm_kubernetes_cluster as per article in below
https://docs.microsoft.com/en-us/azure/aks/spot-node-pool
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: