Follow these steps to configure and install
Traefik Ingress custom resources
for accessing your K8ssandra cluster’s repair interface (provided by Cassandra
Kubernetes cluster with the following elements deployed:
See the Configuring Kind for an example of how to set up a local installation.
DNS name where the repair service should be listening.
Note if you do not have a DNS name available, consider using a service like xip.io to generate a domain name based on the ingress IP address. For local Kind clusters this may look like
repair.127.0.0.1.xip.iowhich would return the address
127.0.0.1during DNS lookup.
k8ssandra Helm chart contains templates for Traefik
IngressRouteTCP Custom Resources. These may be enabled at any time either
values.yaml file or via command-line flags.
ingress: traefik: # Set to `true` to enable the templating of Traefik ingress custom resources enabled: false # Repair service repair: # Note this will **only** work if `traefik.enabled` is also `true` enabled: true # Name of the Traefik entrypoints where we want to source traffic. entrypoints: - web # Hostname Traefik should use for matching requests. host: repair.k8ssandra.cluster.local
host parameter, this is where the DNS name must be provided. You will reference this DNS when accessing Reaper in a Web URL.
If you maintain a values.yaml or traefik.values.yaml file, change the
ingress.traefik.enabled Boolean from
true. Or, specify
--set ingress.traefik.enabled=true on the helm install command line.
Enabling Traefik Ingress
Traefik ingress may be enabled on the command-line or via a
The K8ssandra team recommends storing this information in a
that may be version controlled and managed in a DevOps friendly manner. Examples
of both approaches are provided below as reference.
# New Install helm install cluster-name k8ssandra/k8ssandra -f traefik.values.yaml # Existing Cluster helm upgrade cluster-name k8ssandra/k8ssandra -f traefik.values.yaml
# New Install helm install cluster-name k8ssandra/k8ssandra \ --set ingress.traefik.enabled=true \ --set ingress.traefik.repair.host=repair.cluster-name.k8ssandra.cluster.local # Existing Cluster helm upgrade cluster-name k8ssandra/k8ssandra \ --set ingress.traefik.enabled=true \ --set ingress.traefik.repair.host=repair.cluster-name.k8ssandra.cluster.local
Validate Traefik Configuration
Note this step is optional. The next step will also prove the configuration is working.
With the ingress routes configured and deployed to Kubernetes we can access the Traefik dashboard to validate the configuration has been picked up and is detecting the appropriate services.
Open your web browser and point it at the Traefik dashboard. This may require
kubectl port-forwardor the steps in our Configuring Kind guide.
Navigate to the HTTP Routers page
There should be an entry representing the hostname based rule created as part of the Helm command. Note the Kubernetes logo to the right of the table indicating it was provisioned via a Kubernetes custom resource.
Navigate to the HTTP Services page
There should be an entry representing the Reaper service. Note the Kubernetes logo to the right of the table indicating it was provisioned via a Kubernetes custom resource.
Check out how to Access the Repair Interface
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.