 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.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.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.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.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.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 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
 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.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.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.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.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.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
 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 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 6.0 Manualzabbix_server instances or nodes, where only one node can be active (working) at a time, while other nodes are on standby, ready to take over in case the current node is stopped or fails. See also: High availability now printed to the console. • It is possible to send longer input parameters, such as HA node name instead of node number. Runtime controls on BSD-based OS 15 Previously, Zabbix server and Zabbix proxy CockroachDB by HTTP • Envoy Proxy by HTTP • HashiCorp Consul Cluster by HTTP • HashiCorp Consul Node by HTTP See setup instructions for HTTP templates. You can get these templates: • In Configuration0 码力 | 1681 页 | 23.19 MB | 1 年前3 Zabbix 6.0 Manualzabbix_server instances or nodes, where only one node can be active (working) at a time, while other nodes are on standby, ready to take over in case the current node is stopped or fails. See also: High availability now printed to the console. • It is possible to send longer input parameters, such as HA node name instead of node number. Runtime controls on BSD-based OS 15 Previously, Zabbix server and Zabbix proxy CockroachDB by HTTP • Envoy Proxy by HTTP • HashiCorp Consul Cluster by HTTP • HashiCorp Consul Node by HTTP See setup instructions for HTTP templates. You can get these templates: • In Configuration0 码力 | 1681 页 | 23.19 MB | 1 年前3
 Zabbix 6.2 Manualrepository for each plugin now contains a dedicated release/6.2 branch (previously, there was only master branch). MariaDB 10.10 support The maximum supported version for MariaDB is now 10.10.X. TimescaleDB status. ha_remove_node=target Remove the high availability (HA) node specified by its name or ID. Note that active/standby nodes cannot be removed. target - name or ID of the node (can be obtained high availability Starting Zabbix server as cluster node Two parameters are required in the server configuration to start a Zabbix server as cluster node: • HANodeName parameter must be specified for each0 码力 | 1689 页 | 22.82 MB | 1 年前3 Zabbix 6.2 Manualrepository for each plugin now contains a dedicated release/6.2 branch (previously, there was only master branch). MariaDB 10.10 support The maximum supported version for MariaDB is now 10.10.X. TimescaleDB status. ha_remove_node=target Remove the high availability (HA) node specified by its name or ID. Note that active/standby nodes cannot be removed. target - name or ID of the node (can be obtained high availability Starting Zabbix server as cluster node Two parameters are required in the server configuration to start a Zabbix server as cluster node: • HANodeName parameter must be specified for each0 码力 | 1689 页 | 22.82 MB | 1 年前3
共 155 条
- 1
- 2
- 3
- 4
- 5
- 6
- 16














 
  
 