Uploaded image for project: 'Service Orchestrator'
  1. Service Orchestrator
  2. SO-680

SO mariadb should use nodeport prefix variable

    XMLWordPrintable

    Details

      Description

      https://git.onap.org/oom/tree/kubernetes/so/charts/mariadb/templates/service.yaml
      nodePort: {{ .Values.global.nodePortPrefix | default "302" }}{{ .Values.service.nodePort }}
      nodePort: {{ .Values.global.nodePortPrefix | default .Values.nodePortPrefix }}{{ .Values.service.nodePort }}

      (+)Test results

      ubuntu@ip-172-31-78-76:~/_dev/20180628-oom-1272-so/oom/kubernetes$ kubectl get services --all-namespaces | grep so
      onap          so                     NodePort    10.43.93.81     <none>        8080:30223/TCP,3904:30225/TCP,3905:30224/TCP,9990:30222/TCP,8787:30250/TCP   15m
      onap          so-db                  NodePort    10.43.152.170   <none>        3306:30252/TCP                                                               15m
      ubuntu@ip-172-31-78-76:~/_dev/20180628-oom-1272-so/oom/kubernetes$ kubectl get pods --all-namespaces | grep so
      onap          onap-so-57d4b4f65c-hvvwf                  2/2       Running   0          15m
      onap          onap-so-db-765df45b64-r22bt               1/1       Running   0          15m
      
      
      ubuntu@ip-172-31-78-76:~/_dev/20180628-oom-1272-so/oom/kubernetes$ git status
      On branch master
      	modified:   so/charts/mariadb/templates/service.yaml
      
      

      see OOM-1272

        Attachments

          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

              People

              Assignee:
              seshukm Seshu Kumar M
              Reporter:
              michaelobrien Michael O'Brien
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: