- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for CONNECT (8.5 sec)
-
docs/en/docs/advanced/websockets.md
There you can set: * The "Item ID", used in the path. * The "Token" used as a query parameter. !!! tip Notice that the query `token` will be handled by a dependency. With that you can connect the WebSocket and then send and receive messages: <img src="/img/tutorial/websockets/image05.png"> ## Handling disconnections and multiple clients
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 6.2K bytes - Viewed (0) -
cni/README.md
- `install-cni` container - copies `istio-cni` and `istio-iptables` to `/opt/cni/bin` - creates kubeconfig for the service account the pod runs under - periodically copy the K8S JWT token for istio-cni on the host to connect to K8S. - injects the CNI plugin config to the CNI config file - CNI installer will try to look for the config file under the mounted CNI net dir based on file name extensions (`.conf`, `.conflist`)
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 03 19:29:42 GMT 2024 - 12.3K bytes - Viewed (0) -
docs/en/docs/deployment/docker.md
So, you would run **multiple containers** with different things, like a database, a Python application, a web server with a React frontend application, and connect them together via their internal network. All the container management systems (like Docker or Kubernetes) have these networking features integrated into them. ## Containers and Processes
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 34K bytes - Viewed (0)