Uploaded image for project: 'Data Collection, Analytics, and Events'
  1. Data Collection, Analytics, and Events
  2. DCAEGEN2-2493

Switch CM container and bootstrap blueprint to use single version of K8s plugin

XMLWordPrintable

      For Guilin release, CM container was loading multiple version of K8s plugin

      /k8splugin/2.0.0/k8splugin-2.0.0-py27-none-linux_x86_64.wgn|/k8splugin/2.0.0/k8splugin_types.yaml \
/k8splugin/3.0.0/k8splugin-3.0.0-py27-none-linux_x86_64.wgn|/k8splugin/3.0.0/k8splugin_types.yaml \
/k8splugin/3.3.0/k8splugin-3.3.0-py27-none-linux_x86_64.wgn|/k8splugin/3.3.0/k8splugin_types.yaml \
/k8splugin/3.4.1/k8splugin-3.4.1-py27-none-linux_x86_64.wgn|/k8splugin/3.4.1/k8splugin_types.yaml \
/k8splugin/3.4.2/k8splugin-3.4.2-py27-none-linux_x86_64.wgn|/k8splugin/3.4.2/k8splugin_types.yaml \

      For H release - need to standardize to load and use single K8s version (3.4.2 being latest guilin version)

       

      Following blueprints must be updated to use 3.4.2 (and use dcae.nodes.ContainerizedServiceComponent)

      k8s-datalake-admin-ui.yaml
      k8s-datalake-feeder.yaml
      k8s-restconf.yaml
      k8s-snmptrap.yaml

       

      02/12/2021 - To use most current version/range applicable for Honolulu

      k8splugin?version=>=3.4.3,<4.0.0

            vv770d vv770d
            vv770d vv770d
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: