Deploying killgrave in kubernetes ecosystem
medlouati opened this issue · comments
Hi,
I'm trying to deploy killgrave in a pod on a kubernetes (Tanzu) plateform.
It deploys well with the following logs :
2022/10/18 13:42:53 imposter /etc/killgrave/imposters/..2022_10_18_13_42_52.903949163/gopher.imp.json loaded
2022/10/18 13:42:53 imposter /etc/killgrave/imposters/gopher.imp.json loaded
2022/10/18 13:42:53 The fake server is on tap now: 0.0.0.0:3000
But any http call from outside the container ends up in a time out.
Here's a call from a pod in the same namespace. My service maps the 300035 as a NodePort to the 3000 by the way :
bash-4.2$ curl -kv -H "Content-Type: text/json" mos-mock-ged.mos.svc.cluster.local:30035/gophers
- About to connect() to mos-mock-ged.mos.svc.cluster.local port 30035 (#0)
- Trying 100.28.252.169...
- Connection timed out
- Failed connect to mos-mock-ged.mos.svc.cluster.local:30035; Connection timed out
- Closing connection 0
curl: (7) Failed connect to mos-mock-ged.mos.svc.cluster.local:30035; Connection timed out
Is there any subtelty in the configuration other than the host : 0.0.0.0 configuration I should try ?
The problem was on my part...
Killgrave works just fine ! (though the PoC of Prism was more conclusive for my company for its swagger handling)
The problem was on my part... Killgrave works just fine !
Glad to read that @medlouati :)
(though the PoC of Prism was more conclusive for my company for its swagger handling)
Do you mean something like #116 ?
Thanks!