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.

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

Telepresence needs to support swap-deployment like functionality for clusters with operational machinery asynchronously updating the targeted deployment. #575

Closed
plombardi89 opened this Issue Apr 9, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@plombardi89
Contributor

plombardi89 commented Apr 9, 2018

We have used Telepresence in a system that has a background process periodically updating deployments with the latest code automagically for users. This causes the deployment that Telepresence uses for its proxy to be clobbered.

@rhs rhs changed the title from Telepresence needs to be resilient in the face of operational machinery changing the world behind it. to Telepresence needs to be resilient in the face of operational machinery changing the deployment behind it. Apr 10, 2018

@rhs rhs changed the title from Telepresence needs to be resilient in the face of operational machinery changing the deployment behind it. to Telepresence needs to swap-deployment like functionality for clusters with operational machinery asynchronously updating all the deployments. Apr 10, 2018

@rhs rhs changed the title from Telepresence needs to swap-deployment like functionality for clusters with operational machinery asynchronously updating all the deployments. to Telepresence needs to support swap-deployment like functionality for clusters with operational machinery asynchronously updating all the deployments. Apr 10, 2018

@rhs rhs changed the title from Telepresence needs to support swap-deployment like functionality for clusters with operational machinery asynchronously updating all the deployments. to Telepresence needs to support swap-deployment like functionality for clusters with operational machinery asynchronously updating deployments. Apr 10, 2018

@rhs rhs changed the title from Telepresence needs to support swap-deployment like functionality for clusters with operational machinery asynchronously updating deployments. to Telepresence needs to support swap-deployment like functionality for clusters with operational machinery asynchronously updating the targeted deployment. Apr 10, 2018

@ark3

This comment has been minimized.

Contributor

ark3 commented Apr 10, 2018

Let's change the way swap-deployment works. See #407 for Piyush's implementation. In summary, copy the deployment, giving it a new name so other machinery won't know about it, but keep the labels such that services will reach the new deployment. Then use kubectl scale to set the original deployment down to zero replicas. If other machinery updates the original deployment, it may scale up again and steal requests from the Telepresence session, but at least that session won't crash mysteriously as it does now.

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