Uploaded image for project: 'Red Hat Service Interconnect (Skupper)'
  1. Red Hat Service Interconnect (Skupper)
  2. SKUPPER-2417

Improve helm chart in a cluster installation

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None

      • Add a variable to allow the user to choose the namespace for the controller.
      • Create a hook to create the namespace for the cluster before deploying the controller.
      • Add tests.

      EDIT:
      This task has been substantially changed to leverage the current config directory and kustomize files:

      • Delete former skupper chart from the repository
      • Generate a script that recreates the skupper chart using kustomize overlays such us namespace/cluster for different scopes
      • Update /config structure to allow the generation of the skupper chart using the script
      • Update Makefile and config.yaml files to include the generation of the skupper chart, and add it as a new artifact of the release
      • Update Makefile and config.yaml files to include the packaging of the network-observer chart and add it as a new artifact of the release
      • Update config.yaml to include the operator-bundle tarball as a new artifact of the release
      • Push skupper and network-observer charts into quay.io and allow them to be listed in ArtifactHub
      • Yaml files generated as artifacts of the release that existed to install skupper without helm, are now generated with kubectl kustomize
      • In the skupper helm chart, the controller will be deployed in the current namespace instead of a namespace created by the chart.

              nluaces@redhat.com Noe Luaces
              nluaces@redhat.com Noe Luaces
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: