Microsoft.ContainerService - kubeProxyConfig isn't returned when preview feature is enabled

[stephybun]

Service: Container Service
API Version: 2022-09-02-preview

We'd like to add support for this feature in Terraform, unfortunately we've run into some issues regarding the behaviour of the API.

As documented in the AKS Cluster Schema Kube Proxy is enabled by default on clusters. When the preview feature is enabled I would expect the API to return kubeProxyConfig in the response if it's enabled, i.e.

"networkProfile": {
...
    "kubeProxyConfig": {
        "enabled": true,
        "mode": "IPTABLES"
    }
...
}

Currently nothing is returned which doesn't accurately reflect the state of the cluster and also means Terraform can't know that Kube Proxy is enabled.

In addition, disabling Kube Proxy by sending

      "kubeProxyConfig": {
        "enabled": false
      }

results in the following response from the API.

"kubeProxyConfig": {}

Which isn't inconsistent with the behaviour of features in the rest of the API, like with AGIC for example.

Would you be able to look into:

1. Adding Kube Proxy to the API response when the preview feature and is enabled and Kube Proxy is enabled.
2. Return "enabled": false instead of an empty dictionary when Kube Proxy is disabled.

Thanks!

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/aks-pm.

Issue Details

---

Service: Container Service
API Version: 2022-09-02-preview

We'd like to add support for this feature in Terraform, unfortunately we've run into some issues regarding the behaviour of the API.

As documented in the AKS Cluster Schema Kube Proxy is enabled by default on clusters. When the preview feature is enabled I would expect the API to return kubeProxyConfig in the response if it's enabled, i.e.

"networkProfile": {
...
    "kubeProxyConfig": {
        "enabled": true,
        "mode": "IPTABLES"
    }
...
}

Currently nothing is returned which doesn't accurately reflect the state of the cluster and also means Terraform can't know that Kube Proxy is enabled.

In addition, disabling Kube Proxy by sending

      "kubeProxyConfig": {
        "enabled": false
      }

results in the following response from the API.

"kubeProxyConfig": {}

Which isn't inconsistent with the behaviour of features in the rest of the API, like with AGIC for example.

Would you be able to look into:

1. Adding Kube Proxy to the API response when the preview feature and is enabled and Kube Proxy is enabled.
2. Return "enabled": false instead of an empty dictionary when Kube Proxy is disabled.

Thanks!

Author:	stephybun
Assignees:	-
Labels:	question, AKS, Service Attention, customer-reported, needs-team-attention, Container Service
Milestone:	-

[navba-MSFT]

Adding Service team to look into this.

@Azure/aks-pm Could you please look into this once you get a chance ?

[husira]

Any updates on this topic?

[MaxAnderson95]

Any news to share on this?

[loomkoom]

Any info on this? It would be great if this could be supported by Terraform.

[mattwilder]

Pinging this issue again as it has been over a year and a half since last update. Is this functionality going to be fixed?