Uploaded image for project: 'Application Authorization Framework'
  1. Application Authorization Framework
  2. AAF-848

Installing Custom certificates in SMS via HELM

XMLWordPrintable

    • El Alto Preliminary

      SMS Certificates have expired and releases like Casablanca which use older certificates will be affected by this:

      Here is a work around for this issue via modifying the Helm Charts:

      Get the certificates

      cd oom/kubernetes/aaf/charts/aaf-sms
      mkdir -p resources/certs

      copy the 2 cert files into that folder from here https://github.com/onap/aaf-sms/tree/master/sms-service/src/sms/certs

      aaf-sms.pub
      aaf-sms.pr
      

      Update the Configmap

      Add the following to the end of templates/configmap.yaml

      ---
      apiVersion: v1
      kind: ConfigMap
      metadata:
        name: {{ include "common.fullname" . }}-certs
        namespace: {{ include "common.namespace" . }}
        labels:
          app: {{ include "common.name" . }}-preload
          chart: {{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}
          release: {{ .Release.Name }}
          heritage: {{ .Release.Service }}
      data:
      {{ tpl (.Files.Glob "resources/certs/*").AsConfig . | indent 2 }}

       Update the Deployment

      Add the following lines in templates/deployment.yaml under volumeMounts:

       

      - mountPath: /sms/certs/aaf-sms.pub
        name: {{ include "common.name" .}}-certs
        subPath: aaf-sms.pub
      - mountPath: /sms/certs/aaf-sms.pr
        name: {{ include "common.name" .}}-certs
        subPath: aaf-sms.pr

      Add the following lines in templates/deployment.yaml under volumes:

      - name : {{ include "common.name" . }}-certs
        configMap:
          name: {{ include "common.fullname" . }}-certs

      This chart is now ready to use the new certificates.

       

            kirankamineni kirankamineni
            kirankamineni kirankamineni
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: