Simply connecting to a Kubernetes Service or a load balancer is nice -- if that is even an option. These days, operators have to contend with hybrid and multi-cloud. Namespaces are not enough; it's not uncommon to operate numerous K8s clusters in a single region with traffic being dynamically routed across multiple control planes. This session dives into the process of identifying requirements for a Kubernetes gateway that needs to handle both HTTP based services as well as hyper-optimized TCP workloads. Attendees will walk away with a working knowledge and a process to develop out ingress solutions that fit their needs, including: Deploying a local K8s cluster with K3d Installing the DataStax Kubernetes Operator for Apache Cassandra with Helm Provisioning and running a multi-node Cassandra cluster Deploying Kong Gateway with Helm Implementing multiple ingress approaches through Kong Gateway, with an accompanying discussion on the pros and cons of each Validation of each approach through an external client application