Interacting with tyk APIs without port forwarding on k8s cluster

Did you resolve this issue?

I’m tempted to use a PVC with RWX permissions. But that means manually editing the helm templates to bind to an existing PVC loaded with a blank config.

Or if you’re really good create the PVC as part of the deployment.

An easier method of course is to not use the K8s svc but manually connect to each gateway and apply the config. The problem with this approach is that there is no shared state for rate limits etc.

If I’d known about this type of limitation I would’ve abandoned this 3 weeks. I even had a call about the paid version believing I had a full functional OSS version.