Hi,

Alertmanager pod is stuck with CrashLoopBackOff in Openshift kubernetes
dualstack environment when the alertmanager service uses the same
port(9094) for TCP and UDP. Same build works fine on Openshift kubernetes
non-dualstack environment.

*Environment:*
Openshift cluster with both IPv4 and IPv6 interface.
Aspenmesh-1.11.8-am4

alertmanager - v0.24.0

*Observation:*

For alertmanager service, when tried with different ports for TCP(9094) and
UDP(9095) the deployment is successful.

*Query:*


   1. Is there a need to use different ports for UDP and TCP protocols for
   alertmanager service when deployed in a dualstack k8s environment?
   2. If yes, how does the configured UDP port affect the traffic flow to
   the alertmanager service?

This issue is happening on a fresh installation(not upgrade/rollback)
In side-car logs of alertmanager pod,

2022-10-18T20:37:45.436549Z     warning envoy config    gRPC config
for type.googleapis.com/envoy.config.listener.v3.Listener rejected:
Error adding/updating listener(s) virtualInbound: error adding
listener '0.0.0.0:15006': filter chain '0.0.0.0_9094' has the same
matching rules defined as '0.0.0.0_9094'
virtualInbound6: error adding listener '[::]:15006': filter chain
'::_9094' has the same matching rules defined as '::_9094'

In istiod logs

2022-10-18T21:39:42.878435Z     info    ads     ADS: new connection
for 
node:naperilg27vzwcchf-yz-nk-sm-111-sm-cpro-alertmanager-0.naperilg27vzwcchf-yz-nk-sm-111-1039
2022-10-18T21:39:42.887110Z     info    ads     CDS: PUSH request for
node:naperilg27vzwcchf-yz-nk-sm-111-sm-cpro-alertmanager-0.naperilg27vzwcchf-yz-nk-sm-111
resources:336 size:365.9kB
2022-10-18T21:39:43.126716Z     info    ads     EDS: PUSH request for
node:naperilg27vzwcchf-yz-nk-sm-111-sm-cpro-alertmanager-0.naperilg27vzwcchf-yz-nk-sm-111
resources:140 size:62.8kB empty:0 cached:140/140
2022-10-18T21:39:43.149105Z     info    ads     LDS: PUSH request for
node:naperilg27vzwcchf-yz-nk-sm-111-sm-cpro-alertmanager-0.naperilg27vzwcchf-yz-nk-sm-111
resources:263 size:648.6kB
2022-10-18T21:39:43.466633Z     info    ads     RDS: PUSH request for
node:naperilg27vzwcchf-yz-nk-sm-111-sm-cpro-alertmanager-0.naperilg27vzwcchf-yz-nk-sm-111
resources:23 size:43.8kB
2022-10-18T21:39:43.466671Z     warn    ads     ADS:LDS: ACK ERROR
naperilg27vzwcchf-yz-nk-sm-111-sm-cpro-alertmanager-0.naperilg27vzwcchf-yz-nk-sm-111-1039
Internal:Error adding/updating listener(s) virtualInbound: error
adding listener '0.0.0.0:15006': filter chain '0.0.0.0_9094' has the
same matching rules defined as '0.0.0.0_9094'
2022-10-18T21:40:48.181115Z     info    ads     ADS:
"10.129.12.58:53080"
naperilg27vzwcchf-yz-nk-sm-111-sm-cpro-alertmanager-0.naperilg27vzwcchf-yz-nk-sm-111-1039
terminated rpc error: code = Canceled desc = context canceled

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/CAAB105SGR7YmsZgUZTbYjvF0KDT7KbfVsBOcs_6VjN-8ke0bHA%40mail.gmail.com.

Reply via email to