Starting with Kong CE 0.13 and the forthcoming EE 0.32, users can now separate control and data planes within a Kong cluster, enhancing flexibility and infrastructure architecture. The control plane handles system instrumentation like pushing configurations and fetching logs, while the data plane deals with the actual traffic being proxied. This separation is akin to the distinction between a factory's conveyor belt operations and its auxiliary logistics and maintenance. With this update, Kong's stateless nodes, which connect to a shared database for configuration, can now be more flexibly managed by configuring ports to allow nodes to function exclusively as control-plane or data-plane nodes. This change enhances component isolation by enabling traffic to flow through one network segment and allowing administration via another, reducing the risk of exposing the Kong admin API to the internet. The new configuration format uses a comma-separated list of addresses with flags, allowing for multiple address/port combinations, and users can now easily create data-plane or control-plane nodes by adjusting the `admin_listen` and `proxy_listen` settings respectively.