Troubleshooting Guide

This troubleshooting guide provides solutions to common issues that may arise while using the EGS platform. If you encounter any problems not covered in this guide, please refer to the official documentation or contact support for further assistance.

Installation Issues

Existing Envoy Proxy CRDs can conflict with newer versions of Envoy Proxy CRD used by SliceNSGateWay

Older versions of Envoy Proxy CRDs (for example, v1alpha2) are incompatible with SliceNSGateway. SliceNSGateway requires v1 CRDs.

Workaround:

For advanced routing needs, manually edit the generated GRPCRoute resource to add method matching, or use HTTPRoute for gRPC traffic.

To resolve conflicts with existing Envoy Proxy CRDs, follow these steps on each cluster where SliceNSGateway is deployed:

1. Delete older CRDs: Delete the tcproute, grpcroute, and envoy proxy CRDs that are older than the version v1.
2. Re-install latest envoy charts: Delete existing envoy charts and re-install envoy helm charts with the configuration shared in the documentation. For more information, see Install Envoy Gateway.
3. Restart the worker-operator: restart the worker operator on each worker cluster on which you performed the Step 1 and Step 2

Workspace NS Gateway

gRPC Weighted Traffic Distribution

Weighted traffic distribution for gRPC routes is a known limitation. Although weight values can be configured in the SliceNSGateway custom resource and are correctly reflected in the generated GRPCRoute resource (for example, a 70/30 split), the runtime traffic distribution does not honor the configured weights.

Workaround:

Use HTTP/HTTPS routes for weighted traffic distribution until gRPC weighted routing is fully supported.

SliceNSGateway gRPC Route Configuration

gRPC route configuration in SliceNSGateway has the following constraints:

• No method/service matching support: The routingRules field does not support gRPC method or service matching. All gRPC traffic is routed using default rules without method-level granularity.
• Missing explicit match configuration: GRPCRoute rules are created without explicit match criteria, which may cause issues with some Envoy Gateway implementations.

Workaround:

For advanced routing needs, manually edit the generated GRPCRoute resource to add method matching, or use HTTPRoute for gRPC traffic.

info

Enhanced gRPC routing capabilities, including service or method matching, will be supported in a future release.