Upgrading from 3.7.0 to 3.11.0 pulumi's throwing new errors about how fields can't be specified:

{
            "urn": "urn:pulumi:deployments-infra-dev-eu::deployments-infra-dev-eu::mpp:Cluster$azure:containerservice/kubernetesCluster:KubernetesCluster::deveu2",
            "message": "error: azure:containerservice/kubernetesCluster:KubernetesCluster resource 'deveu2' has a problem: \"addon_profile.0.http_application_routing.0.http_application_routing_zone_name\": this field cannot be set\n",
            "severity": "error"
        },
        {
            "urn": "urn:pulumi:deployments-infra-dev-eu::deployments-infra-dev-eu::mpp:Cluster$azure:containerservice/kubernetesCluster:KubernetesCluster::deveu2",
            "message": "error: azure:containerservice/kubernetesCluster:KubernetesCluster resource 'deveu2' has a problem: Can not parse \"addon_profile.0.oms_agent.0.log_analytics_workspace_id\" as a resource id: Cannot parse Azure ID: parse \"\": empty url\n",
            "severity": "error"
        },
        {
            "urn": "urn:pulumi:deployments-infra-dev-eu::deployments-infra-dev-eu::mpp:Cluster$azure:containerservice/kubernetesCluster:KubernetesCluster::deveu2",
            "message": "error: azure:containerservice/kubernetesCluster:KubernetesCluster resource 'deveu2' has a problem: \"addon_profile.0.oms_agent.0.oms_agent_identity\": this field cannot be set\n",
            "severity": "error"
        }

but I never specified those anyway, they've just appeared.