3 ms·
Great question! For local development - we recommend connecting to a dev k8s cluster, which is easy enough to setup. CI is actually something I get really exc
by sjezewski 10y ago
Great question!
For local development - we recommend connecting to a dev k8s cluster, which is easy enough to setup.
CI is actually something I get really excited about. Similary for CI you can have a separate k8s cluster for any tests you need to run. But because we version everything, you can run 'unit tests' on sample data sets that you know should be rock solid ... and also 'integration tests' on the _same_versioned_data_ you would see in production.
- jdoliner 10y agoJust to clarify, a dev k8s cluster doesn't require anything more than a stock installation of Docker. K8s has actually gotten pretty easy to test against recently thanks to being deployable as containers.
- eterps 10y agoDo you have some examples or links to share?
- jdoliner 10y agoThis is the script we use to start k8s for tests: https://github.com/pachyderm/pachyderm/blob/master/etc/kube/start-kube-docker.sh https://github.com/pachyderm/pachyderm/blob/master/etc/kube/... There's k8s docs on this somewhere but unfortunately they move around a lot so I can't find a link right now. It's just 1 docker run command though and you're good to go.