4 ms·
What tool are you using to setup k8s? I really recommend kops - because it takes care of some cloud specific config clashes. For example, it users the carrier
by sandGorgon 9y ago
What tool are you using to setup k8s? I really recommend kops - because it takes care of some cloud specific config clashes.
For example, it users the carrier grade subnet 100.64 for AWS because other up subnet conflict.
I have moved on from k8s to docker swarm because of the ingress complexity in k8s. I'm hoping some of the momentum behind Istio will solve it in the future.
- buahahaha 9y agoit's clear the ingress complexity is what's burning them here. It's just a simple exposed port mixup causing that error rate.
- ahawkins 9y agoWe considered that as well. We have a smoke test for the chart that hits each service with a generic ping RPC. I thought that was good enough upon reevaluating it. The generic ping RPC comes from an inherited service which means _any_ or our Thrift services could respond correctly with a pong. Which means the correct service may run on the same port. I verified this is not the case. I'll update the smoke test to use a different test rpc as regression for this possibility.
- ahawkins 9y agoWe are using Kops. It's worked well for us so far.