Help deploying Kong in k8s with read-only filesystem

Questions
1

We are trying to get Kong working on k8s host with a read-only filesystem. We can create read/write volumeMounts but can’t get the Kong container to ready status.

If we curl the status:

curl localhost:8100/status

curl: (52) Empty reply from server

command terminated with exit code 52

I’m not sure if I should be trying to troubleshoot by reverse-engineering the source-code, or asking if there is a guide to deploying on read-only k8s.

Any help or suggestions welcome :slight_smile:

2

Additional error that might help:

2023/05/11 09:58:54 [error] 1128#0: *1218 [lua] broker.lua:111: run(): failed to init socket: failed to flush response header: nginx output filter error, client: unix:, server: kong_worker_events, request: "GET / HTTP/1.1", host: "localhost"