VPC-Native Networking support after upgrade do-k8s

[Khuman2]

Hello, community!

I've created my do-k8s cluster more than year ago following by example.
I upgraded the cluster up to v1.33.1.
Time to switch from nginx incress controller to Gateway API comes and I did following the doc
But I got the situation when my Gateway is in Pending status. The case is fully described here and the solution is "Recreating the cluster fixes the issue"

But I don't want to recreate the cluster.
terraform state show digitalocean_kubernetes_cluster.do-k8s output:

resource "digitalocean_kubernetes_cluster" "do-k8s" {
    auto_upgrade                     = false
    cluster_subnet                   = "10.244.0.0/16"
    created_at                       = "2024-08-24 09:34:04 +0000 UTC"
    destroy_all_associated_resources = false
    endpoint                         = "https://<id>.k8s.ondigitalocean.com"
    ha                               = false
    id                               = "<id>"
    ipv4_address                     = null
    kube_config                      = (sensitive value)
    name                             = "do-k8s"
    region                           = "fra1"
    registry_integration             = false
    service_subnet                   = "10.245.0.0/16"
    status                           = "running"
    surge_upgrade                    = true
    tags                             = [
        "env:production",
    ]
    updated_at                       = "2025-11-14 19:20:36 +0000 UTC"
    urn                              = "do:kubernetes:<id>"
    version                          = "1.33.1-do.5"
    ...
}

So, it seems like my cluster has default cluster_subnet and service_subnet.
I'm not sure are they VPC-native?
There are no cilium-gateway-controller pod in my k8s too. Do I have any chances to initiate cilium-gateway-controller and get the gateway ready without re-creation the k8s cluster?