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
Monitor the [Echo Server](https://github.com/soketi/echo-server) container for memory allowance and new connections when running in Kubernetes.
12
+
Monitor the [pWS server](https://github.com/soketi/pws) container for memory allowance and new connections when running in Kubernetes.
13
13
14
14
## 🤔 What does this controller solve?
15
15
16
-
If you run Echo Server standalone in a cluster, at scale, you might run into capacity issues: RAM usage might be near the limit and even if you decide to horizontally scale the pods, new connections might still come to pods that are near-limit and run into OOM at some point.
16
+
If you run pWS standalone in a cluster, at scale, you might run into capacity issues: RAM usage might be near the limit and even if you decide to horizontally scale the pods, new connections might still come to pods that are near-limit and run into OOM at some point.
17
17
18
-
Running Network Watcher inside the same pod will solve the issues by continuously checking the Echo Server Usage API, labeling the pods that get over a specified threshold with `echo.soketi.app/accepts-new-connections: "no"`, so that the services watching for the pods will ignore them if also checking for this label:
18
+
Running Network Watcher inside the same pod will solve the issues by continuously checking the pWS Server Usage API, labeling the pods that get over a specified threshold with `pws.soketi.app/accepts-new-connections: "no"`, so that the services watching for the pods will ignore them if also checking for this label:
[Network Watcher is available via Docker](https://hub.docker.com/r/soketi/network-watcher). Use the images to run them into your cluster and use this project to develop the application.
41
41
42
-
[Network Watcher also comes with the Echo Server Helm chart](https://github.com/soketi/charts/tree/master/charts/echo-server). It just needs to be turned on if you need the network watcher and the according service annotations will be appended automatically.
42
+
[Network Watcher also comes with the pWS Server Helm chart](https://github.com/soketi/charts/tree/master/charts/pws). It just needs to be turned on if you need the network watcher and the according service annotations will be appended automatically.
43
43
44
44
## 🚀 Installation
45
45
@@ -59,7 +59,7 @@ $ php application network:watch
59
59
| - | - | - | - |
60
60
|`POD_NAMESPACE`|`--pod-namespace`|`default`| The Pod namespce to watch. |
61
61
|`POD_NAME`|`--pod-name`|`some-pod`| The Pod name to watch. |
62
-
|`ECHO_APP_PORT`|`--echo-app-port`|`6001`| The port number for the [Echo Server](https://github.com/soketi/echo-server) app. |
62
+
|`SERVER_PORT`|`--server-port`|`6001`| The port number for the [pWS server](https://github.com/soketi/pws). |
63
63
|`MEMORY_PERCENT`|`--memory-percent`|`75`| The threshold (in percent) that, once reached, the Pod will be marked as "not ready" to evict any new connections or requests. |
64
64
|`CHECKING_INTERVAL`|`--checking-interval`|`1`| The amount of seconds to wait between API checks. |
65
65
|`TEST_MODE`|`--test`| - | Run a single check rather than a continous loop of checks. |
0 commit comments