Configuring nodebalancer within kubernetes with the linode-cloud-controller-manager install

Nobody has claimed this yet.

Hi, i have create some linode and added them to a VPC and a Subnet, in my plain cluster(not using LKE)
i have install the linode-cloud-controller-manager and have serious problem when trying to provision a nodebalancer.
the linodes doesn't have any private IP so when i try to provision a nodebalancer like this :

```
apiVersion: v1
kind: Service
metadata:
name: my-service
annotations:
service.beta.kubernetes.io/linode-loadbalancer-backend-ipv4-range: "10.0.1.8/30"
service.beta.kubernetes.io/linode-loadbalancer-backend-vpc-name: "k8s-vpc"
service.beta.kubernetes.io/linode-loadbalancer-backend-subnet-name: "k8s-nodes"
spec:
type: LoadBalancer
ports:
- port: 80
targetPort: 8080
selector:
app: my-app
```

i get Error

> Syncing load balancer: failed to ensure load balancer: [400] [configs[0].nodes[0].address] Must begin with 192.168; [configs[0].nodes[1].address] Must begin with 192.168;

so i have changed to helm chart to try to install the linode cloud controller with the corresponding values for vpc and subnet has it is said here : [Linode cloud controller helm installation](https://github.com/linode/linode-cloud-controller-manager/blob/main/docs/getting-started/helm-installation.md)
tried both approches with the route controller or just setting the vpcs but this time getting a weird message saying

> Nodebalancer is not allowed within a VPC

Start with the Kubernetes Service manifest in the issue and the linked docs/getting-started/helm-installation.md instructions, then reproduce the NodeBalancer provisioning errors on a plain Kubernetes cluster. Trace how the VPC, subnet, backend IP range, and route-controller values are interpreted; done means the supported configuration and resulting behavior are documented or the reported error is corrected.

Written by the indexing model from the issue text.