DHCP library and CLI server with multiple backends. All IP addresses are served as DHCP reservations. There are no leases.

• Tink gRPC server
  • This backend is the main use case. It pulls hardware data from the Tink gRPC API for use in serving DHCP clients.
• Tink Kubernetes CRDs
  • This backend is also the main use case. It pulls hardware data from Kubernetes CRDs for use in serving DHCP clients.
• File based
  • This backend is for mainly for testing and development. It reads a file for hardware data to use in serving DHCP clients. See example.yaml for the data model.
• Cacher server
  • This backend is mainly for backward compatibility in Boots. It pulls hardware data from the Cacher API for use in serving DHCP clients. It is planned for deprecation in Boots.

DHCP Reservation: A fixed IP address that is reserved for a specific client.

DHCP Lease: An IP address, that can potentially change, that is assigned to a client by the DHCP server. The IP is typically pulled from a pool or subnet of available IP addresses.