Merge pull request #388 from MegaGM/patch-1

jondubois · web-flow · commit fee1a27b278c · 2018-03-16T22:49:52.000+01:00
broken link
diff --git a/scc-guide.md b/scc-guide.md
@@ -110,4 +110,4 @@ The **scc-state** instance does not handle any pub/sub messages and so it is not
 
 Note that you can launch the services in any order you like but if your state server is not available, you may get harmless `Socket hung up` warnings on other instances (while they keep trying to reconnect) until **scc-state** becomes available again.
 
-The **socketcluster** deployment in https://github.com/SocketCluster/socketcluster/kubernetes/ uses podAntiAffinity rule to ensure only one socketcluster instance is scheduled for any given kubernetes node. This may be preferred, since we want to run on as many cores as possible.
+The **socketcluster** deployment in https://github.com/SocketCluster/socketcluster/tree/master/kubernetes uses podAntiAffinity rule to ensure only one socketcluster instance is scheduled for any given kubernetes node. This may be preferred, since we want to run on as many cores as possible.

Original file line number	Diff line number	Diff line change
`@@ -110,4 +110,4 @@ The scc-state instance does not handle any pub/sub messages and so it is not`
`110`	`110`
`111`	`111`	Note that you can launch the services in any order you like but if your state server is not available, you may get harmless `Socket hung up` warnings on other instances (while they keep trying to reconnect) until scc-state becomes available again.
`112`	`112`
`113`		`-The socketcluster deployment in https://github.com/SocketCluster/socketcluster/kubernetes/ uses podAntiAffinity rule to ensure only one socketcluster instance is scheduled for any given kubernetes node. This may be preferred, since we want to run on as many cores as possible.`
	`113`	`+The socketcluster deployment in https://github.com/SocketCluster/socketcluster/tree/master/kubernetes uses podAntiAffinity rule to ensure only one socketcluster instance is scheduled for any given kubernetes node. This may be preferred, since we want to run on as many cores as possible.`