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
Copy file name to clipboardExpand all lines: README.md
+12-4Lines changed: 12 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,16 +25,24 @@ Flags:
25
25
"backend": "HOST:PORT"
26
26
}
27
27
```
28
-
28
+
*`POST /defaultRoute`
29
+
Registers a default route to the given backend. JSON body is structured as:
30
+
```json
31
+
{
32
+
"backend": "HOST:PORT"
33
+
}
34
+
```
29
35
*`DELETE /routes/{serverAddress}`
30
36
Deletes an existing route for the given `serverAddress`
31
37
32
38
## Using kubernetes service auto-discovery
33
39
34
40
When running `mc-router` as a kubernetes pod and you pass the `--in-kube-cluster` command-line argument, then
35
-
it will automatically watch for any services annotated with `mc-router.itzg.me/externalServerName`. The value
36
-
of the annotation will be registered as the external hostname Minecraft clients would used to connect to the
37
-
routed service. The service's clusterIP and target port are used as the routed backend.
41
+
it will automatically watch for any services annotated with
42
+
-`mc-router.itzg.me/externalServerName` : The value of the annotation will be registered as the external hostname Minecraft clients would used to connect to the
43
+
routed service. The service's clusterIP and target port are used as the routed backend.
44
+
-`mc-router.itzg.me/defaultServer` : The service's clusterIP and target port are used as the default if
45
+
no other `externalServiceName` annotations applies.
38
46
39
47
For example, start `mc-router`'s container spec with
0 commit comments