Cilium v1.10 Documentationpackets emitted by the application containers, allowing to validate the identity at the receiving node. Security identity management is performed using a key-value store. Secure access to and from external means that each host can allocate IPs without any coordination between hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts EDT-based (Earliest Departure Time) rate-limiting with eBPF for container traffic that is egressing a node. This allows to significantly reduce transmission tail latencies for applications and to avoid locking0 码力 | 1307 页 | 19.26 MB | 1 年前3
Cilium v1.11 Documentationpackets emitted by the application containers, allowing to validate the identity at the receiving node. Security identity management is performed using a key-value store. Secure access to and from external means that each host can allocate IPs without any coordination between hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts EDT-based (Earliest Departure Time) rate-limiting with eBPF for container traffic that is egressing a node. This allows to significantly reduce transmission tail latencies for applications and to avoid locking0 码力 | 1373 页 | 19.37 MB | 1 年前3
Cilium v1.9 Documentationpackets emitted by the application containers, allowing to validate the identity at the receiving node. Security identity management is performed using a key-value store. Secure access to and from external means that each host can allocate IPs without any coordination between hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts EDT-based (Earliest Departure Time) rate-limiting with eBPF for container traffic that is egressing a node. This allows to significantly reduce transmission tail latencies for applications and to avoid locking0 码力 | 1263 页 | 18.62 MB | 1 年前3
Cilium v1.8 Documentationpackets emitted by the application containers, allowing to validate the identity at the receiving node. Security identity management is performed using a key-value store. Secure access to and from external means that each host can allocate IPs without any coordination between hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts io/docs/setup/learning-environment/minikube/] to demonstrate deployment and operation of Cilium in a single-node Kubernetes cluster. The minikube VM requires approximately 5GB of RAM and supports hypervisors like0 码力 | 1124 页 | 21.33 MB | 1 年前3
Cilium v1.7 Documentationpackets emitted by the application containers, allowing to validate the identity at the receiving node. Security identity management is performed using a key-value store. Secure access to and from external means that each host can allocate IPs without any coordination between hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts io/docs/getting-started-guides/minikube/] to demonstrate deployment and operation of Cilium in a single-node Kubernetes cluster. The minikube VM requires approximately 5GB of RAM and supports hypervisors like0 码力 | 885 页 | 12.41 MB | 1 年前3
Cilium v1.6 Documentationpackets emitted by the application containers, allowing to validate the identity at the receiving node. Security identity management is performed using a key-value store. Secure access to and from external means that each host can allocate IPs without any coordination between hosts. The following multi node networking models are supported: Overlay: Encapsulation-based virtual network spanning all hosts io/docs/getting-started-guides/minikube/] to demonstrate deployment and operation of Cilium in a single-node Kubernetes cluster. The minikube VM requires approximately 5GB of RAM and supports hypervisors like0 码力 | 734 页 | 11.45 MB | 1 年前3
Cilium v1.5 DocumentationTroubleshoo�ng Monitoring & Metrics Exported Metrics Cilium as a Kubernetes pod Cilium as a host-agent on a node Troubleshoo�ng Component & Cluster Health Connec�vity Problems Policy Troubleshoo�ng Automa�c Diagnosis network packets emi�ed by the applica�on containers, allowing to validate the iden�ty at the receiving node. Security iden�ty management is performed using a key-value store. Secure access to and from external This means that each host can allocate IPs without any coordina�on between hosts. The following mul� node networking models are supported: Overlay: Encapsula�on based virtual network spawning all hosts.0 码力 | 740 页 | 12.52 MB | 1 年前3
Zabbix 1.8 Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 2 Proxy v.s. Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 5 Configuration of a single Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 6 Switching feature might be very handy for automatic monitoring of new Cloud nodes. As soon as you have a new node in the Cloud Zabbix will automatically start collection of performance and availability data of the0 码力 | 485 页 | 9.28 MB | 1 年前3
Zabbix 2.0 Manualprocess that may collect data on behalf of Zabbix server, taking some processing load off of the server node - a full Zabbix server configured as an element within a hierarchy of distributed monitoring; it are calculated in a similar way, but this also depends on a total number of child nodes linked to a node. Time synchronisation It is very important to have precise system date on server with Zabbix running Parameter Description Group name Enter a unique host group name. The name must be unique within a Zabbix node. Hosts Select hosts, members of the group. A host group may have zero, one or more hosts. 2 Inventory0 码力 | 791 页 | 9.66 MB | 1 年前3
Zabbix 2.2 Manual• zabbix[java„] • zabbix[process,, , ] (alerter, db watchdog, escalator, node watcher, proxy poller, timer processes aren’t supported, but two new processes are supported - data usage in environments with huge numbers of problem triggers and host groups. • In node-based environments, a duplicating Node column has been removed from trigger popups in the System status frontend widget process that may collect data on behalf of Zabbix server, taking some processing load off of the server node - a full Zabbix server configured as an element within a hierarchy of distributed monitoring; it 0 码力 | 918 页 | 11.28 MB | 1 年前3
共 114 条
- 1
- 2
- 3
- 4
- 5
- 6
- 12













