minimal-kong-controller.yaml installs Kong open source with the ingress controller in DB-less mode.
minimal-kong-standalone.yaml installs Kong open source and Postgres with no controller.
minimal-kong-enterprise-dbless.yaml installs Kong for Kubernetes with Kong Enterprise with the ingress controller in DB-less mode.
minimal-k4k8s-with-kong-enterprise.yaml installs Kong for Kubernetes with Kong Enterprise with the ingress controller and PostgreSQL. It does not enable Enterprise features other than Kong Manager, and does not expose it or the Admin API via a TLS-secured ingress.
full-k4k8s-with-kong-enterprise.yaml installs Kong for Kubernetes with Kong Enterprise with the ingress controller in PostgreSQL. It enables all Enterprise services.
minimal-kong-hybrid-control.yaml and minimal-kong-hybrid-data.yaml install separate releases for hybrid mode control and data plane nodes, using the built-in PostgreSQL chart on the control plane release. They require some pre-work to create certificates and configure the control plane location. See comments in the file headers for additional details.

Note that you should install the control plane release first if possible: data planes must be able to talk with a control plane node before they can come online. Starting control planes first is not strictly required (data plane nodes will retry their connection for a while before Kubernetes restarts them, so starting control planes second, but around the same time will usually work), but is the smoothest option.
minimal-kong-enterprise-hybrid-control.yaml and minimal-kong-enterprise-hybrid-data.yaml install separate releases of Kong Enterprise for hybrid mode control and data plane nodes, using the built-in PostgreSQL chart on the control plane release. They require some pre-work to create certificates and configure the control plane location. See comments in the file headers for additional details.

Note that you should install the control plane release first if possible: data planes must be able to talk with a control plane node before they can come online. Starting control planes first is not strictly required (data plane nodes will retry their connection for a while before Kubernetes restarts them, so starting control planes second, but around the same time will usually work), but is the smoothest option.

All Enterprise examples require some level of additional user configuration to install properly. Read the comments at the top of each file for instructions.