You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
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.
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
The text was updated successfully, but these errors were encountered: