Enabling TMF Microservice Ingress

After installing a TM Forum (TMF) microservice, you can keep the API accessible only within the cluster using the created microservice, or you can expose the microservice to external traffic.

To expose TMF microservices to external traffic, you must create a Kubernetes ingress definition.

The following example shows a tmf-party-management-ingress definition:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: tmf-party-management-ingress
spec:
  rules:
  - http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: tmf-party-tmf-party-management
            port:
              number: 8080
The following example shows a tmf-service-activation-management-ingress definition:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: tmf-service-activation-management-ingress
spec:
  rules:
  - http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: tmf-service-activation-tmf-service-activation-management
            port:
              number: 8080
The following example shows a tmf-usage-consumption-management-ingress definition:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: tmf-usage-consumption-management-ingress
spec:
  rules:
  - http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: tmf-usage-consumption-tmf-usage-consumption-management
            port:
              number: 8080