remove third-party DHCP example

this is sort of broken and does not make too much sense

Signed-off-by: Emanuele Di Pascale <[email protected]>

Author: edipascale

docs/user-guide/vpcs.md

@@ -46,12 +46,6 @@ spec:
       isolated: true # Makes subnet isolated from other subnets within the VPC (doesn't affect VPC peering)
       restricted: true # Causes all hosts in the subnet to be isolated from each other
 
-    third-party-dhcp: # Another subnet
-      dhcp:
-        relay: 10.99.0.100/24 # Use third-party DHCP server (DHCP relay configuration), access to it could be enabled using a static External
-      subnet: "10.10.2.0/24"
-      vlan: 1002
-
     dhcp-relay-to-other-vpc: # Another subnet with DHCP relay to a separate VPC
       dhcp:
         relay: 10.20.20.200/32 # IP address to reach the DHCP server in the target VPC
@@ -109,17 +103,6 @@ If the `disableDefaultRoute` is set to `true`, and the VPC is `mode: l3vni` the
 fabric DHCP server will send routes to the end hosts so that they can reach
 other hosts inside of the VPC via the VPC gateway.
 
-### Third-party DHCP server configuration
-
-To use a third-party DHCP server, configure `spec.subnets.<subnet>.dhcp.relay`. Additional information is
-added to the DHCP packet forwarded to the DHCP server to make it possible to identify the VPC and subnet. This
-information is added under the RelayAgentInfo (option 82) in the DHCP packet. The relay sets two suboptions in the
-packet:
-
-* _VirtualSubnetSelection_ (suboption 151) is populated with the VRF which uniquely identifies a VPC on the Hedgehog
-  Fabric and will be in `VrfV<VPC-name>` format, for example `VrfVvpc-1` for a VPC named `vpc-1` in the Fabric API.
-* _CircuitID_ (suboption 1) identifies the VLAN which, together with the VRF (VPC) name, maps to a specific VPC subnet.
-
 ### DHCP Relay to another VPC
 
 It is possible to configure DHCP relay for a VPC subnet towards a DHCP server in another VPC. To do so: