Trying to set up ingress with nginx about k8ssandra HOT 2 OPEN

HTTP ingress is not going to work here as Cassandra uses TCP. There are ways to do TCP ingress with nginx (and other ingress controllers). Typically it requires either adding a configmap to the ingress or using a custom resource definition provided via the ingress instead of the standard k8s ingress objects. (Note the Gateway API should help with this in the future).

Now when you get that configured you must decide how you route from the ingress to pods. The naive solution is to let it round robin, but this will introduce latency as the drivers prefer to connect to a node that houses the data for the query and use it as a coordinator. Additionally, should you run multiple C* clusters within a single k8s cluster how do you route to the different clusters? One option is to put each cluster on its own port within the ingress. Alternatively you could leverage TLS with SNI to allow for direct routing from the ingress to the appropriate node. It is worth noting that if you go this route there is additional configuration needed within the client application to configure TLS appropriately AND logic to update the routing within your ingress should you C* cluster topology change.

That's not to say it isn't possible, and we have some examples of how to accomplish this.

from k8ssandra.

So with all that being said what type of example would you prefer?

• TLS w/ SNI routing
• Port-based routing

from k8ssandra.