Uploaded image for project: 'Helm'
  1. Helm
  2. HELM-269

OCP multi cluster support

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Helm, UI
    • OCP multi cluster support
    • False
    • False
    • To Do
    • 25% To Do, 0% In Progress, 75% Done

      Problem:

      The OCP Dev Console will enable multi-cluster support. Each backend of the console will need to support getting the k8 context from the selected cluster rather than the current cluster where is running.

      Goal:

      Enable Console Helm backend to support multi-cluster environment.

      Why is it important?

      Helm feature will be disabled if customer is in a multi-cluster environment but helm backend does not support multi-cluster.

      Use cases

      Customer in a multi-cluster environment selects a target cluster and tries to install a helm chart. The chart should be deployed in the target cluster, not on the cluster where console backend runs.

      Acceptance criteria

      Helm is enabled and able to deploy charts to target cluster in a multi-cluster environment.

      Dependencies (External/Internal)

      Console team will write common code handling the context resolution to be used by each backend api. This will make sure the code is maintainable across all api backends.

      Design Artifacts

      Exploration

      Note

              Unassigned Unassigned
              dperaza@redhat.com David Peraza
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: