Pods monitoring with zabbix agent and running agent as sidecars #2765
Unanswered
davidbetko
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, has anyone encountered an implementation where you run a Zabbix agent for monitoring in the sidecars section of a PostgreSQL pod deployment? I am currently trying to deploy it, but the operator is struggling with this, and the pods keep restarting with the following error:
time="2024-09-23T08:42:25Z" level=warning msg="error while syncing cluster state: could not sync statefulsets: could not recreate pods: skipping switchover: no switchover candidate found" cluster-name=mondev/postgres-dev-cluster pkg=cluster worker=0
time="2024-09-23T08:42:25Z" level=error msg="could not sync cluster: could not sync statefulsets: could not recreate pods: skipping switchover: no switchover candidate found" cluster-name=mondev/postgres-dev-cluster pkg=controller worker=0
sidecars implementation:
sidecars:
- name: zabbix-agent2
image: zabbix/zabbix-agent2:ubuntu-7.0.3
resources:
limits:
cpu: 250m
memory: 256M
requests:
cpu: 150m
memory: 100M
env:
- name: ZBX_SERVER_HOST
value: "IP address"
- name: ZBX_SERVER_PORT
value: "10051" # Zabbix server port
- name: ZBX_PASSIVE_ALLOW
value: "true" # Enable passive checks
- name: ZBX_ACTIVE_ALLOW
value: "false" # Enable active checks
- name: ZBX_HOSTNAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: ZBX_PASSIVE_PORT
value: "10050"
- name: ZBX_ACTIVE_PORT
value: "10051"
ports:
- containerPort: 10050
protocol: TCP
name: zbx-pas
- containerPort: 10051
protocol: TCP
name: zbx-actv
Beta Was this translation helpful? Give feedback.
All reactions