-
Bug
-
Resolution: Done
-
Medium
-
Dublin Release
-
None
-
None
-
SDNC Fr Sp4:1/6-1/24
CDS Blueprint Processor doesn't work with NodePorts service type as it's missing default value for the port nodePort suffix.
Currently, during helm deploy step, it would try to use port of only NodePortPrefix
For my overrides had to apply
sdnc:
enabled: true
cds:
cds-blueprints-processor:
service:
type: NodePort
nodePort: "99"
so I assume the values.yaml in blueprint processor neds to have nodePort defined.