-
Task
-
Resolution: Done
-
Medium
-
None
see: https://wiki.onap.org/display/DW/Ingress+configuration+options
Additional parameters to modify the BaseAddess value of the composed Ingress URL
Problem:
- If ONAP is installed on multiple clusters (e.g. clusterA, clusterB)
- and a wildcard-certificate for the baseurl domain exists (e.g. *.simpledemo.onap.org)
- you cannot create cluster specific Ingress URLs for the ONAP services (e.g. sdnc-dgbuilder-ui.simpledemo.onap.org)
Solution:
- Add a cluster specific post/prefix to the baseAddr of the service to create uniqe URLs instead changing each service baseAddr
- Results using "postfix" e.g.
- sdnc-dgbuilder-ui-clusterA.simpledemo.onap.org
- sdnc-dgbuilder-ui-clusterB.simpledemo.onap.org
Allow customized Ingress Gateway Ports
Problem:
- Ingress Gateways usually expose HTTP ports (80, 443), can be extended in non-NGINX gateways (e.g. Istio, Traefik)
- The existing Ingress template only supports the 80/443 ports
- If non-HTTP ports need to be exposed (e.g. Kafka Bootstrap, SDNC CallHome/TLS), this is not possible
- see: External Kafka Access via Ingress
Solution:
- In the component's ingress configuration the exposed port needs to be configurable
- the Ingress template needs to generate the respective Gateway/VC resources