Configure Traefik ingress
|We haven't updated the descriptions in this topic yet for the K8ssandra Operator implementation. The content below applies to the earlier K8ssandra 1.4.x deployments. We will provide an updated version of this K8ssandra Operator topic soon. In the meantime, please join our K8ssandra Community Discord channel and we'll answer your questions there. Thanks!|
External connectivity can be tricky with Kubernetes. There are many solutions in this space, ranging from some that focus on pure HTTP workloads, to others that allow for custom TCP and UDP routing.
Kubernetes provides an
Ingress resource type, but does not provide an
Ingress Controller. Instead Kubernetes operators must decide on the Ingress controller they choose to run, whether it is provided by a cloud vendor, a software vendor, or an open-source project.
Transport Layer Security (TLS) to Traefik Ingress integrates with your existing infrastructure components and configures itself automatically and dynamically. Traefik handles advanced Ingress deployments including Mutual TLS (mTLS) of TCP with Server Name Indication (SNI) and User Datagram Protocol (UDP). Operators define rules for routing traffic to downstream systems through Kubernetes
Ingress objects or more specific
Custom Resource Definitions. K8ssandra supports deploying
IngressRoute objects as part of a deployment to expose metrics, repair, and Cassandra interfaces. See the topics listed below.
The provided Traefik ingress solutions are not recommended for production environments. As an alternative, consider port forwarding. It’s another way to provide external access to resources that have been deployed by K8ssandra in your Kubernetes environment. The
kubectl port-forward command does not require an Ingress/Traefik to work. See:
Traefik ingress topics:
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.