Good morning,
I have my zabbix server running on a Virtual Machine with IP address: 192.168.24.128. This is connected to another Virtual Machine with IP address 192.168.24.129, that has a Zabbix agent installed and correctly connected to the server.
Inside this virtual machine, Kubernetes has been installed with Flannel as Network Plugin, and an Ubuntu pod has been deployed and is running. This pod has a new Zabbix agent installed and running inside. In order to have access to the pod from outside the cluster, a NodePort service has been created, with port and targetPort: 8081 and nodePort: 30170.
When adding the new host to the server dashboard (connecting to the Interface 192.168.24.129:30170), the Status turns to Not available and an error appears: "Received empty response from Zabbix Agent at [192.168.24.129]. Assuming that agent dropped connection because of access permissions."
Zabbix agent configuration (/etc/zabbix/zabbix_agentd.conf) has just been modified in the following lines to be able to connect to the server:
# Server=
Server=127.0.0.1,192.168.24.128
ListenPort=8081
# ServerActive=
ServerActive=192.168.24.128
Hostname=ubuntu
In the server dashboard, the host has been added with the following features:
If checking with tcpdump the packets received inside the pod, we can see that they are indeed arriving inside, but the pod (with internal IP: 10.244.0.128) is sending some RST, ACK messages, which was a bit strange compared to the tcpdump captures observed in the working agent.
Any help or advice would be greatly appreciated, as I am very interested in monitoring pods and would love to have this working as soon as possible.
I have my zabbix server running on a Virtual Machine with IP address: 192.168.24.128. This is connected to another Virtual Machine with IP address 192.168.24.129, that has a Zabbix agent installed and correctly connected to the server.
Inside this virtual machine, Kubernetes has been installed with Flannel as Network Plugin, and an Ubuntu pod has been deployed and is running. This pod has a new Zabbix agent installed and running inside. In order to have access to the pod from outside the cluster, a NodePort service has been created, with port and targetPort: 8081 and nodePort: 30170.
When adding the new host to the server dashboard (connecting to the Interface 192.168.24.129:30170), the Status turns to Not available and an error appears: "Received empty response from Zabbix Agent at [192.168.24.129]. Assuming that agent dropped connection because of access permissions."
Zabbix agent configuration (/etc/zabbix/zabbix_agentd.conf) has just been modified in the following lines to be able to connect to the server:
# Server=
Server=127.0.0.1,192.168.24.128
ListenPort=8081
# ServerActive=
ServerActive=192.168.24.128
Hostname=ubuntu
In the server dashboard, the host has been added with the following features:
If checking with tcpdump the packets received inside the pod, we can see that they are indeed arriving inside, but the pod (with internal IP: 10.244.0.128) is sending some RST, ACK messages, which was a bit strange compared to the tcpdump captures observed in the working agent.
Any help or advice would be greatly appreciated, as I am very interested in monitoring pods and would love to have this working as soon as possible.
Attached Files
Comment