chore!(ingress): drop http server; v2.0.0 #165
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This release drops the HTTP server used in FlowProxy for dealing with system
requests. Now only the TCP server exists. It marks a breaking change in
FlowProxy, because backwards compatibility is not maintained anymore.
that also the
readyz/infoz/livezendpoint are now unsupported as well.Healthchecks will be performed by sending a special packet to the TCP server,
see fix(socket/rep): correct cleanup on FIN + ping support chainbound/msg-rs#140.
infozendpoint for portdiscovery has been dropped, and the socket address returned from BuilderHub is
assumed to be for the TCP server.
--system-listen-addr-tcp(SYSTEM_LISTEN_ADDR_TCP) has beendropped.
--system-listen-addr-http(SYSTEM_LISTEN_ADDR) has been renamedto
--system-listen-addr, with same environment variable name, and it now isused to bind the TCP server.
--http.client-pool-size(CLIENT_POOL_SIZE) has been removed sincethere are no more HTTP clients used for forwarding orders to peers.