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

connectivity: proposal for degraded connectivity behavior #10

Closed
junr03 opened this issue Apr 11, 2019 · 5 comments
Closed

connectivity: proposal for degraded connectivity behavior #10

junr03 opened this issue Apr 11, 2019 · 5 comments

Comments

@junr03
Copy link
Member

junr03 commented Apr 11, 2019

Design an API for envoy to be aware of OS level signals (e.g connection to WiFi vs mobile network, app backgrounded) in order for envoy to react appropriately.

@junr03 junr03 transferred this issue from another repository May 2, 2019
@junr03 junr03 added this to the v0.2 "Primo" milestone May 2, 2019
@stale
Copy link

stale bot commented Jun 2, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 2, 2019
@junr03 junr03 removed stale labels Jun 3, 2019
@costinm
Copy link

costinm commented Jun 19, 2019

+1 - include battery info as well if possible. All this would be very valuable on the control plane -
based on network type (metered, speed) and battery status it can push different configs.

As a proposal, a method "setMetadata" to update the bootstrap node.metadata, so the management
server can make decisions based on the current information. The method would just update the meta and do some update on the XDS to make sure the server gets the new status.

Technically it is possible to restart envoy with a different bootstrap config whenever the network or battery config changes.

Note that net config changes also result in new interfaces and IPs that envoy might need to bind to.

@stale
Copy link

stale bot commented Jul 19, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 19, 2019
@stale
Copy link

stale bot commented Jul 26, 2019

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

@stale stale bot closed this as completed Jul 26, 2019
@rebello95 rebello95 reopened this Jul 26, 2019
@stale stale bot removed the stale label Jul 26, 2019
@junr03
Copy link
Member Author

junr03 commented Oct 22, 2019

Done in #442.

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

No branches or pull requests

5 participants