New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove the synclet as default #3245

Closed

nicks opened this issue Apr 27, 2020 · 1 comment

Labels

Member

nicks commented Apr 27, 2020 •

edited

The Synclet is implemented as a privileged sidecar that talks directly to the Docker socket.

This is proving more and more difficult to make work, because it's inconsistent with the overall direction of the Kubernetes ecosystem:

The privileged permission is generally discouraged and unexpected.
The sidecar approach is not a good fit for this particular use-case, because it breaks a bunch of behavior. The Kubernetes community is hopeful for ephemeral containers (https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/20190212-ephemeral-containers.md)
Modern Kubernetes clusters generally don't use Docker-shim at all, so don't even have a Docker socket.

We shouldn't drive new users to the synclet

nicks added the enhancement label

nicks mentioned this issue

connection to synclet stops working #2182

Closed

nicks mentioned this issue

Improve node read permission error message, provide a way to disable #3280

Closed

Contributor

maiamcc commented Jul 22, 2020

Resolved by #3563

maiamcc closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment