The common.containerPort template (defined of kubernetes/common/common/templates/_pod.tpl) creates the containerPort definitions in container specs for deployments and stateful sets. It uses values from the "services" section of a component's values.yaml file. It does not supply a "protocol" field for the containerPort definition, meaning that the protocol will default to TCP.
This is a problem for the DCAEGEN2 snmptrap-collector, which exposes a UDP port.
The l4_protocol field in the definition of a port in the "services" section of a component's values.yaml file can be used to set the protocol field in the containerPort specification.
The common.containerPort template (defined of kubernetes/common/common/templates/_pod.tpl) creates the containerPort definitions in container specs for deployments and stateful sets. It uses values from the "services" section of a component's values.yaml file. It does not supply a "protocol" field for the containerPort definition, meaning that the protocol will default to TCP.
This is a problem for the DCAEGEN2 snmptrap-collector, which exposes a UDP port.
The l4_protocol field in the definition of a port in the "services" section of a component's values.yaml file can be used to set the protocol field in the containerPort specification.