This repository was archived by the owner on Jan 30, 2020. It is now read-only.
[fleet-grpc] Fallback in firewalled environments #1598
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 ( 6E65 etcd based coordination) if new agents are not able to talk to the engine over grpc.
Related to #1426
The text was updated successfully, but these errors were encountered: