Skip to main content
Tungsten Clustering

Verification & Monitoring

Check Deployment Status​

View all resources:

shell> kubectl -n tungsten-connector get all

Check pod status

shell> kubectl -n tungsten-connector get pods

View pod details

shell> kubectl -n tungsten-connector describe pod <pod-name>

View Logs​

Follow logs

shell> kubectl -n tungsten-connector logs -f deployment/tungsten-connector

View recent logs

shell> kubectl -n tungsten-connector logs --tail=100 deployment/tungsten-connector

Test Connectivity​

First, get the LoadBalancer external IP:

shell> kubectl -n tungsten-connector get service tungsten-connector

Wait for EXTERNAL-IP to be assigned. Example output:

# NAME                 TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)
# tungsten-connector   LoadBalancer   10.96.123.45    203.0.113.10    3306:30001/TCP,3307:30002/TCP...

Once the EXTERNAL-IP is assigned, test connectivity to each port, replacing [EXTERNAL-IP] with the actual LoadBalancer IP

  • MySQL Read-Write Port (3306)

    shell> mysql -h [EXTERNAL-IP] -u app_user -psecret -P 3306 -e "SELECT @@hostname"

  • MySQL Read-Only Port (3307)

    shell> mysql -h [EXTERNAL-IP] -u app_user -psecret -P 3307 -e "SELECT @@hostname"

  • Prometheus Metrics (8093)

    shell> curl http://[EXTERNAL-IP]:8093/metrics

  • REST API (8096)

    shell> curl -u app_user:secret http://[EXTERNAL-IP]:8096/api/info

Troubleshooting​

Pod Not Starting​

If the Pod is not starting, check events:

shell> kubectl -n tungsten-connector describe pod <pod-name>

and check logs for further information on why the pod is failing:

shell> kubectl -n tungsten-connector logs <pod-name>

Common Issues​

Missing SSL Certificates

  • If security is enabled, ensure all certificate files are added to secret-security.yaml

Database Connection Failed

  • Verify database hostnames are resolvable via DNS
  • If using hostAliases, verify the IPs are correct and databases are reachable
  • Check network policies allow connectivity from the connector pod

Authentication Failed

  • Check application-password in configmap-tungsten.yaml matches database credentials

Liveness/Readiness Probe Failures

  • Connector may need more time to start. Check logs for errors

Clean Up​

To delete all resources:

shell> kubectl delete namespace tungsten-connector

Or delete individually:

shell> kubectl delete -f .