Troubleshooting Semantic Guardrails

This section describes the connection errors that may occur while testing Semantic Guardrails integration using Ingress.

Verifying Ingress status

To verify the Ingress status, run the following command.

kubectl get ingress -n pty-semantic-guardrails -o wide

Verify the is accessability of load balancer

To verify the load balancer hostname

To verify the load balancer hostname, run the following command.

LB_HOST=$(kubectl get ingress nfa-semantic-guardrails -n pty-semantic-guardrails -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')
echo "Load balancer: $LB_HOST"

Testing direct load balancer connection

To test direct load balancer connection, run the following command.

curl -k https://$LB_HOST/pty/semantic-guardrails/v1.1/health -H "Host: eclipse.aws.protegrity.com"

Port Forward for Local Testing

To forward the port for local testing run the following command.

kubectl port-forward svc/semantic-guardrails-service 8001:8001 -n pty-semantic-guardrails
curl http://localhost:8001/pty/semantic-guardrails/v1.1/health