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
As @elmiko said: as i recall, the headless service uses a different port for connection. like the main service is for using the 7077 port to communicate with the master, the workers need a different port for communicating with the master. i think we probably need to review what pieces are needed. i think we _might_ be able to condense those ports into the main service as it looks like a service can handle multiple ports. but i'm not 100% sure on that. that link is for an s2i driver app, but i think the same could be applied to the cluster that's the other issue too, the workers need fqdn back to the driver
The text was updated successfully, but these errors were encountered:
As @elmiko said:
as i recall, the headless service uses a different port for connection. like the main service is for using the 7077 port to communicate with the master, the workers need a different port for communicating with the master. i think we probably need to review what pieces are needed. i think we _might_ be able to condense those ports into the main service as it looks like a service can handle multiple ports. but i'm not 100% sure on that. that link is for an s2i driver app, but i think the same could be applied to the cluster that's the other issue too, the workers need fqdn back to the driver
The text was updated successfully, but these errors were encountered: