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.

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

[ws-proxy] Don't use DNS but service endpoints #6441

Closed
csweichel opened this issue Oct 28, 2021 · 3 comments · Fixed by #6462
Closed

[ws-proxy] Don't use DNS but service endpoints #6441

csweichel opened this issue Oct 28, 2021 · 3 comments · Fixed by #6462
Assignees
@aledbf
Labels
aspect: performance anything related to performance component: ws-proxy groundwork: awaiting deployment team: workspace Issue belongs to the Workspace team
Projects
[DEPRECATED] Product Engineering Grou...

Comments

@csweichel
Copy link
Contributor

Right now we use the kubernetes internal DNS to resolve endpoints for workspaces. This incurs the DNS propagation delays and is a bit fickle. Instead we could use the service endpoints, or even pods directly to determine where a request should go.
@csweichel csweichel added component: ws-proxy aspect: performance anything related to performance team: workspace Issue belongs to the Workspace team labels Oct 28, 2021
@aledbf aledbf mentioned this issue Oct 30, 2021
Merged
@csweichel
Copy link
Contributor Author

/schedule

@roboquat
Copy link
Contributor

@csweichel: Issue scheduled in the workspace team (WIP: 0)

In response to this:

/schedule

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@csweichel
Copy link
Contributor Author

/assign @aledbf

@roboquat roboquat moved this from Inbox to Scheduled in [DEPRECATED] Product Engineering Groundwork Oct 31, 2021
@roboquat roboquat moved this from Scheduled to In Progress in [DEPRECATED] Product Engineering Groundwork Oct 31, 2021
@roboquat roboquat moved this from Scheduled to In Progress in [DEPRECATED] Product Engineering Groundwork Oct 31, 2021
@roboquat roboquat moved this from In Progress to In Review in [DEPRECATED] Product Engineering Groundwork Nov 2, 2021
@roboquat roboquat moved this from In Progress to Inbox in [DEPRECATED] Product Engineering Groundwork Nov 2, 2021
@csweichel csweichel moved this from Inbox to In Review in [DEPRECATED] Product Engineering Groundwork Nov 3, 2021
@roboquat roboquat moved this from Done to Awaiting Deployment in [DEPRECATED] Product Engineering Groundwork Nov 5, 2021
@roboquat roboquat moved this from Awaiting Deployment to Done in [DEPRECATED] Product Engineering Groundwork Nov 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aledbf aledbf

Labels
aspect: performance anything related to performance component: ws-proxy groundwork: awaiting deployment team: workspace Issue belongs to the Workspace team
Projects
No open projects
[DEPRECATED] Product Engineering Grou...
Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ws-proxy] Decouple ws-proxy from ws-manager gitpod-io/gitpod
4 participants
@aledbf @csweichel @roboquat and others