terraform-provider-azurerm
terraform-provider-azurerm copied to clipboard
Support for setting runtimeRequestTimeout in kubelet_config
Is there an existing issue for this?
- [X] I have searched the existing issues
Community Note
- Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
kubelet_config in azurerm_kubernetes_cluster.default_node_pool and azurerm_kubernetes_cluster_node_pool does not allow setting the kubelet configuration runtimeRequestTimeout. This can lead to problems e.g. when using large docker images.
runtimeRequestTimeout is the timeout for all runtime requests except long running requests - pull, logs, exec and attach. Default: "2m"
(from https://kubernetes.io/docs/reference/config-api/kubelet-config.v1beta1/#kubelet-config-k8s-io-v1beta1-KubeletConfiguration).
New or Affected Resource(s)/Data Source(s)
kubernetes_cluster, azurerm_kubernetes_cluster_node_pool
Potential Terraform Configuration
resource "azurerm_resource_group" "example" {
name = "example-resources"
location = "West Europe"
}
resource "azurerm_kubernetes_cluster" "example" {
name = "example-aks1"
location = azurerm_resource_group.example.location
resource_group_name = azurerm_resource_group.example.name
dns_prefix = "exampleaks1"
default_node_pool {
name = "default"
node_count = 1
vm_size = "Standard_D2_v2"
kubelet_config {
runtime_request_timeout= "2m"
}
}
}
resource "azurerm_kubernetes_cluster_node_pool" "example" {
name = "internal"
kubernetes_cluster_id = azurerm_kubernetes_cluster.example.id
vm_size = "Standard_DS2_v2"
node_count = 1
kubelet_config {
runtime_request_timeout= "2m"
}
}
References
No response
is there any workaround how to increase runtimeRequestTimeout?
@stephybun "sdk/not-yet-supported" because the azure rest api does not support "runtimeRequestTimeout" in its kubelet config for agent pool creation?
@Johannesm299 that is correct. If it isn't available in the AKS API then it isn't something that we can support.
I would suggest heading over to the AKS repo and raising a feature request there so the service team can take a look at adding it.
Thanks for taking the time to open this issue. It looks like the behavior you requested is not supported by the underlying AKS API so I am going to close it for now. If you create a request on AKS repo, feel free to add the link here. When it gets added, we can reopen this request or you can create a new one.
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.