-
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
PreconditionFailedEtagMismatch - Manual outbound rule deleted from LB at AKS changed #13886
Comments
Hi @fraozy! Interesting issue, to manage expectations, I might not have the solution for you. I have a few questions though :) First of all, I'd really like to know why there is an outbound rule specified in the first place to get the scenario straight, as it is normally not advised to specify anything on the AKS resources themselves, unless it's really necessary. If possible, I would advise to modify egress traffic with UDR instead of manually creating an outbound rule (not completely sure if I understand your use-case here). If there is a use-case which should be supported in Terraform, I'd like to know. Secondly, it is interesting to know what the error exactly is and what triggered it. I'm interested if this is a reconciliation error which would bite you potentially in a later stage (for instance when updating AKS to a higher version) even if you'd do this in the Portal, or that it's something specifically for Terraform (which I find unlikely). Let's start with that, and work further from there 👍🏽 |
Hello @aristosvo. About your points:
Thanks a lot. |
Well, that's something @fabianofranz! Can't this be solved with Public IPs for a specific node pool or a different subnet for your nodepool? It sounds like a mission impossible to do it from outside the cluster, by using K8s LoadBalancer services you may be able to do a bit more. I can't blame or relate this problem in any way on I'm sorry, I think that is all we can do for you from here. |
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. |
I have a manual "backend pool" (aks01_app_nodepool) and "outbound rule" (avmOutboundRule) created at kubernetes load balancer, but when I made any update (tags, paramters) at AKS or nodepool, the outbound rule (avmOutboundRule) manually created is deleted (the backend pool (aks01_app_nodepool)manually created remain).
The error at kubernetes load balance is:
Terraform (and AzureRM Provider) Version
Terraform 1.08
AzureRM Provider 2.79.1
Affected Resource(s)
azurerm_kubernetes_cluster
azurerm_kubernetes_cluster_node_pool
Terraform Configuration Files
- Manually created rule at kubernetes load balancer:
Debug Output
Panic Output
Expected Behaviour
The manually created outbound rule (avmOutboudRule) remain when AKS or nodepool are updated using terraform.
Actual Behaviour
The outbound rule (avmOutboudRule) is deleted on any update.
Steps to Reproduce
Execute any update at kubernetes_cluster module (outbound_ports_allocated, tags or any other parameters) and execute the terraform apply
Important Factoids
I created a case with Azure support and they indicated that no issue exist at their side (I made the same steps direcly from Azure Portal and problem does not happen).
The text was updated successfully, but these errors were encountered: