Skip to main content
added 75 characters in body
Source Link
Mike Ounsworth
  • 59.3k
  • 21
  • 162
  • 214

One argument that comes to mind is that often designers want the cluster to be transparentagnostic about which node a user is connected toto; ie the user gets the same output regardless of which node did the processing, sessions started on one node can be load-balanced to a different node without the user knowing, etc. Having different certificates for each node would prevent this.

One argument that comes to mind is that often designers want the cluster to be transparent about which node a user is connected to, sessions started on one node can be load-balanced to a different node, etc. Having different certificates for each node would prevent this.

One argument that comes to mind is that often designers want the cluster to be agnostic about which node a user is connected to; ie the user gets the same output regardless of which node did the processing, sessions started on one node can be load-balanced to a different node without the user knowing, etc. Having different certificates for each node would prevent this.

Source Link
Mike Ounsworth
  • 59.3k
  • 21
  • 162
  • 214

One argument that comes to mind is that often designers want the cluster to be transparent about which node a user is connected to, sessions started on one node can be load-balanced to a different node, etc. Having different certificates for each node would prevent this.