Environment Information

• Terraform version: "N/A"
• Rancher2 Provider version: "main"
• Rancher version: "N/A"
• Operating System of the Rancher Node: "N/A"
• Operating System of the machine running Terraform: "N/A"
• Kubernetes Distro (k3s/rke2): "N/A"
• Kubernetes Version: "N/A"
• Infrastructure Provider (AWS/GCP/vSphere/etc): "Linode"
• What is the scope of the token given to the provider? "N/A"

Describe the Problem

rancher2_machine_config_v2 currently exposes legacy linode_config fields such as create_private_ip, but it does not expose the newer Linode machine driver options needed for:

• Linode interface/VPC networking
• Linode metadata user_data / cloud-init support

That means users cannot configure these features through Terraform even when the Rancher/Linode machine driver supports them.

This blocks Terraform users from adopting the newer Linode networking model while still using rancher2_machine_config_v2 for downstream cluster provisioning.

The provider needs schema, expand/flatten, validation, tests, and docs updates for the Linode machine config fields added by these Linode machine driver PRs:

• feat: add VPC interface networking and firewall controls linode/docker-machine-driver-linode#220
• feat: add cloud-init user data support via Linode Metadata linode/docker-machine-driver-linode#222

Expected provider support includes:

• use_interfaces
• vpc_subnet_id
• vpc_private_ip
• public_interface_firewall_id
• vpc_interface_firewall_id
• user_data

Compatibility expectations:

• Keep existing legacy create_private_ip support intact.
• Prevent invalid combinations between legacy private IP mode and interface/VPC mode.
• Document that the new fields depend on the corresponding Linode machine driver support landing first.