TLDR: I think it could be good to start looking at possible replacement of the ISC DHCP-relay agent (dhcrelay) used by VyOS since its EOL.
Longer:
It turns out that the ISC DHCP-relay agent (dhcrelay) used in VyOS have been deprecated for some time even if its still available in Debian repositories:
https://packages.debian.org/bookworm/isc-dhcp-relay
ISC has decided to stop maintaining the client and relay parts of isc-dhcp, and they will be removed after the 4.4.3 release, keeping only the server component. Please, consider using an alternative for isc-dhcp-relay (dhcrelay). More information can be found in the ISC official announcement: https://www.isc.org/blogs/dhcp-client-relay-eom/
The above blog-post (last updated January 2022) states that:
There are forks of the ISC client and relay included in operating system packages, and there are also alternative client and relay implementations available. For example: * Roy Marples offers a dhcpcd client. * OpenBSD distributes a DHCP client apparently based on the ISC DHCP client, that has been updated by Henning Brauer. FreeBSD also packages that client. * BusyBox distributes a very small client, suitable for embedded applications. * OpenDHCP reportedly includes a relay. OpenWRT packages that and a DHCP forwarder maintained by Scott Logan. * Dibbler, which is also no longer maintained, includes a client and relay as well as a server. * ISC is also considering developing a new relay based on Kea DHCP code.
So far (April 2024) it seems that ISC have not created any DHCP-relay agent based on the KEA DHCP code.
Another option to evaluate (except for the list from the blog-post) would be to use dnsmasq for this task:
https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
--dhcp-relay=<local address>[,<server address>[#<server port>]][,<interface] Configure dnsmasq to do DHCP relay. The local address is an address allocated to an interface on the host running dnsmasq. All DHCP requests arriving on that interface will we relayed to a remote DHCP server at the server address. It is possible to relay from a single local address to multiple remote servers by using multiple --dhcp-relay configs with the same local address and different server addresses. A server address must be an IP literal address, not a domain name. If the server address is omitted, the request will be forwarded by broadcast (IPv4) or multicast (IPv6). In this case the interface must be given and not be wildcard. The server address may specify a non-standard port to relay to. If this is used then --dhcp-proxy should likely also be set, otherwise parts of the DHCP conversation which do not pass through the relay will be delivered to the wrong port. Access control for DHCP clients has the same rules as for the DHCP server, see --interface, --except-interface, etc. The optional interface name in the --dhcp-relay config has a different function: it controls on which interface DHCP replies from the server will be accepted. This is intended for configurations which have three interfaces: one being relayed from, a second connecting the DHCP server, and a third untrusted network, typically the wider internet. It avoids the possibility of spoof replies arriving via this third interface. It is allowed to have dnsmasq act as a DHCP server on one set of interfaces and relay from a disjoint set of interfaces. Note that whilst it is quite possible to write configurations which appear to act as a server and a relay on the same interface, this is not supported: the relay function will take precedence. Both DHCPv4 and DHCPv6 relay is supported. It's not possible to relay DHCPv4 to a DHCPv6 server or vice-versa. The DHCP relay function for IPv6 includes the ability to snoop prefix-delegation from relayed DHCP transactions. See --dhcp-script for details.
Otherwise out of the box it would probably be a good thing if the OpenBSD fork can be used by VyOS (even if VyOS is linuxbased).