Updating API-Gateway Service

To update API-Gateway service:

1. Login to Kubernetes cluster master node using ssh command.
2. Run the following command to edit svc yaml file for API-Gateway:

   kubectl edit svc <NEF_NAME>-api-gateway -n <NEF_NAME_SPACE>

   Table 3-1 Variables

   Field	Description
   NEF_NAME	The --name value used in helm install command
   NEF_NAME_SPACE	The --namespace value used in helm install command

   Following is an sample content that displays in API-Gateway edit window

   1 # Please edit the object below. Lines beginning with a '#' will be ignored,
    2 # and an empty file will abort the edit. If an error occurs while saving this file will be
    3 # reopened with the relevant failures.
    4 #
    5 apiVersion: v1
    6 kind: Service
    7 metadata:
    8   creationTimestamp: 2019-04-02T08:17:51Z
    9   labels:
   10     category: common
   11     io.kompose.service: <NEF_NAME>-pcf-api-gateway-service
   12   name: <NEF_NAME>-pcf-api-gateway-service
   13   namespace: <NEF_NAME_SPACE>
   14   resourceVersion: "25282719"
   15   selfLink: /api/v1/namespaces/<NEF_NAME_SPACE>/services/<NEF_NAME>-pcf-api-gateway-service
   16   uid: cec8f019-551f-11e9-acc3-a0369f714f30
   17 spec:
   18   clusterIP: 10.233.63.101
   19   externalTrafficPolicy: Cluster
   20   ports:
   21   - name: http
   22     nodePort: 32314
   23     port: 8080
   24     protocol: TCP
   25     targetPort: 8080
   26   selector:
   27     io.kompose.service: <NEF_NAME>-pcf-api-gateway-service
   28   sessionAffinity: None
   29   type: NodePort
   30 status:
   31   loadBalancer: {}

3. Add two new lines after line 7, after metadata:

   annotations:

   metallb.universe.tf/address-pool: <ADDRESS_POOL_NAME>

   Note:

   • As per user MetalLB setting, select an appropriate pool name to replace the variable,<ADDRESS_POOL_NAME>.

   • annotation: line must be kept vertical align with line 16, while following line, metallb.universe.tf/address-pool: <ADDRESS_POOL_NAME> must be kept vertical align with line 10. If vertical align restriction failed to follow this rule, the svc yaml file update may fail.

4. Replace line 29 text, type: NodePort with type: LoadBalancer.

   Following is a sample content after replacing line 29.

   1 # Please edit the object below. Lines beginning with a '#' will be ignored,
    2 # and an empty file will abort the edit. If an error occurs while saving this file will be
    3 # reopened with the relevant failures.
    4 #
    5 apiVersion: v1
    6 kind: Service
    7 metadata:
    8   creationTimestamp: 2019-04-02T08:17:51Z
    9   labels:
   10     category: common
   11     io.kompose.service: <NEF_NAME>-pcf-api-gateway-service
   12   name: <NEF_NAME>-pcf-api-gateway-service
   13   namespace: <NEF_NAME_SPACE>
   14   resourceVersion: "25282719"
   15   selfLink: /api/v1/namespaces/<NEF_NAME_SPACE>/services<NEF_NAME>-pcf-api-gateway-service
   16   uid: cec8f019-551f-11e9-acc3-a0369f714f30
        annotations:
          metallb.universe.tf/address-pool: <ADDRESS_POOL_NAME>
   17 spec:
   18   clusterIP: 10.233.63.101
   19   externalTrafficPolicy: Cluster
   20   ports:
   21   - name: http
   22     nodePort: 32314
   23     port: 8080
   24     protocol: TCP
   25     targetPort: 8080
   26   selector:
   27     io.kompose.service: <NEF_NAME>-pcf-api-gateway-service
   28   sessionAffinity: None
   29   type: LoadBalancer
   30 status:
   31   loadBalancer: {}

   1. Quit vim editor and save changes. A new API-Gateway pod starts up.

      In the new pod, following sample content displays. Note that if the EXTERNAL-IP is available then the load balancer setting for API-Gateway service works.

      NAME                     TYPE           CLUSTER-IP      EXTERNAL-IP    PORT(S)                                                   AGE
      <NEF_NAME>-pcf-api-gateway       LoadBalancer   10.xxx.xx.xx    10.xxx.xxx.xx   80:30000/TCP,443:30001/TCP,8001:30373/TCP,8444:31448/TCP    4d

Update cm-service

Follow the same process logic to update svc yaml for <NEF_NAME>-pcf-cm-service.