Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-3251

common.containerPorts template doesn't set protocol

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • New Delhi Release
    • Montreal Release
    • charts
    • None
    • Hide

      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.

       

      Show
      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.  

          jackl Jack Lucas
          jackl Jack Lucas
          Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

            Created:
            Updated:
            Resolved: