ksync connected a developer's local directory to files inside a running Kubernetes container. Editing the local source could update that container without rebuilding and redeploying an image for every small change. It was useful for a deliberately managed development loop with remote dependencies. The project is archived, and the resulting filesystem could differ from the recorded image, so this workflow should not be confused with a reproducible production deployment.
Current guidance
The vapor-ware/ksync link resolves to ksync/ksync, which GitHub marks archived. The project synchronized a local directory into a running Kubernetes container to shorten development cycles. It did not produce a new immutable application image for each edit, so the running filesystem could differ from the deployment’s recorded image.
Before retiring an existing setup, identify local-to-remote mappings, cluster-side components and any host access they require. Preserve developer changes that exist only in the synchronized directory. Review compatibility with the actual container runtime rather than assuming Docker-era installation instructions apply to a modern cluster.
A replacement development workflow should explicitly choose between rebuilding images, synchronizing selected files and executing remote commands. Test file deletion, permissions, pod replacement and loss of the development connection, and exclude credentials or large generated directories from synchronization. Keep the workflow away from production data and shared service accounts. The archived client’s one-line installer is historical material, and no verified official successor or current runtime support commitment is established by this review.
Historical upstream link check · 2026-10-09
The recorded upstream address redirects to https://github.com/ksync/ksync and returned HTTP 200 on 2026-10-09. GitHub marks ksync/ksync as archived. This confirms the repository's read-only archive state; any successor or supported distribution needs separate evidence. GitHub resolves the old repository identity to ksync/ksync. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
ksync speeds up developers who build applications for Kubernetes. It transparently updates containers running on the cluster from your local checkout. This enables developers to use their favorite IDEs, such as Atom or Sublime Text to work from inside a cluster instead of from outside it. There is no reason to wait minutes to test code changes when you can see the results in seconds.
If you’ve been wanting to do something like docker run -v /foo:/bar with Kubernetes, ksync is for you!
Using ksync is as simple as:
- ksync create --pod=my-pod local_directory remote_directory to configure a folder you’d like to sync between your local system and a specific container running on the cluster.
- ksync watch to connect to the cluster and start updating the container.
- Use your favorite editor, like Atom or Sublime Text to modify the application. It will auto-reload for you remotely, in seconds.
Demo
See it in action, below or try it out in your browser using this Katacoda scenario:
Sources & further reading
Spotted something that needs another look?
Help improve this page →