Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

[fleet-grpc] Fallback in firewalled environments #1598

Open
hectorj2f opened this issue May 27, 2016 · 0 comments
Open

[fleet-grpc] Fallback in firewalled environments #1598

hectorj2f opened this issue May 27, 2016 · 0 comments

Comments

@hectorj2f
Copy link
Contributor

A major blocker for the integration of fleet-grpc, as enabled by default, into coreos images is the new port used to communicate grpc servers/clients.

In some environments, there might be firewalls on which the required port by gRPC is closed. Therefore, fleet-grpc should be intelligent enough to detect this behavior and fallback to the old behaviour (etcd based coordination) if new agents are not able to talk to the engine over grpc.

Related to #1426

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

No branches or pull requests

2 participants