Doug

@MichalLytek @Hebilicious can we get an update in the description of this issue and/or the labels applied? Seeing a "high priority bug" open for ~2 years is, in my view,...

based on a comment from a telepresence contributor on another issue I unfortunately cannot find, it seems that telepresence v2 does not support proxying pods, hence the hostname of the...

@thallgren first, regarding your most recent comment, that's a worthwhile caveat to call out, but irrelevant in this case. FWIW I don't even care about intercepting incoming traffic to the...

@thallgren if you're asserting that proxying local traffic to cluster pods fronted by headless services is an already supported feature, this would still be a bug, not a feature request....

@thallgren new issue opened in #2814

this may be one of the few things GitLab does much better IMO, but I can appreciate (enough to suggest this be configurable rather than a new default, but not...

@swetharepakula what are the recommended steps to reliably recover a system experiencing this issue, separate from the preventative configuration you recommended? is deleting the service, ingress, and deployment sufficient, then...

how is this issue still open after 3 years? the overlap between pulumi users and k8s users must be huge. can someone from pulumi have a look at and prioritize...

there is no known universal workaround as neither `"` nor `,` are escaped, so even json-supported values are not properly json serialized

@cindymullins-dw can you explain why this is categorized a feature request as opposed to a bug report as it was intended? comments from maintainers as well as documentation suggest this...