Skip to content

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

Open
@stephybun

Description

@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!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    AKSContainer ServiceService AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions