Microsoft.ContainerService/managedClusters@2023-08-02-preview: Updating a Kubernetes Cluster using Bicep shows the properties.controlPlanePluginProfiles being removed from the cluster

[BenjaminEllett]

Resource Type

Microsoft.ContainerService/managedClusters

Api Version

2023-08-02-preview

Issue Type

Missing property(s)

Other Notes

When I update my Kubernetes cluster using Bicep, it claims I am removing the following settings:

properties: {
controlPlanePluginProfiles: {
'azure-monitor-metrics-ccp': {
enableV2: true
}

        karpenter: {
            enableV2: true
        }
    }

}

When I add the settings to my Bicep file, I get the following error:

WARNING: C:\HB4\EnterpriseHackBoxInfrastructure\Deployment\Bicep\kubernetes-services-and-web-site\single-kubernetes-cluster-module.bicep(307,9) : Warning BCP037: The property "controlPlanePluginProfiles" is not allowed on objects of type "ManagedClusterProperties". Permissible properties include "apiServerAccessProfile", "azureMonitorProfile", "creationData", "diskEncryptionSetID", "enableNamespaceResources", "enablePodSecurityPolicy", "fqdnSubdomain", "guardrailsProfile", "httpProxyConfig", "ingressProfile", "linuxProfile", "nodeResourceGroupProfile", "podIdentityProfile", "privateLinkResources", "publicNetworkAccess", "serviceMeshProfile", "upgradeSettings", "workloadAutoScalerProfile". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]

Here is what I want:

1. I either want the Kubernetes Bicep resource to stop exposing controlPlanePluginProfiles or to start supporting it so the warning goes away.

2. I would also like a way to surpress Bicep warnings on a case by case basis. In this case, I would like to be able to tell Bicep that setting controlPlanePluginProfiles is OK because I do not want to change its settings inadvertently when I deploy.

Bicep Repro

No response

Confirm

• I have read the troubleshooting guide and looked for duplicates.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @qike-ms, @jwilder, @thomas1206, @seanmck. Please see https://aka.ms/biceptypesinfo for troubleshooting help.