Skip to content
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

Add support for intercepting daemonset #3360

Open
mkirouac opened this issue Sep 28, 2023 · 0 comments
Open

Add support for intercepting daemonset #3360

mkirouac opened this issue Sep 28, 2023 · 0 comments
Labels
t:feature New feature or enhancement request

Comments

@mkirouac
Copy link

Please describe your use case / problem.
I have a service that needs to always be co-located on the same node as a different service. Because I use GKE AutoPilot, this is not something that is supported out of the box, hence we are using a daemonset to achieve this behavior. The pattern used is documented here: https://wdenniss.com/strict-pod-co-location

Since telepresence does not support intercepting daemonsets, I am not able to use it for this particular service running as a deamonset.

Describe the solution you'd like
I would like to have a way to intercept daemonsets.

Describe alternatives you've considered
Right now our only alternative is not to use telepresence for this service.

Versions (please complete the following information)

  • telepresence: 2.9.5
  • k8: 1.26.6-gke.1700
@cindymullins-dw cindymullins-dw added the t:feature New feature or enhancement request label Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:feature New feature or enhancement request
Projects
None yet
Development

No branches or pull requests

2 participants