Uploaded image for project: 'Server Deployments and Scale'
  1. Server Deployments and Scale
  2. SCALE-138

Ability to spin up Bitbucket Mesh cluster individually

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • Environment - Kubernetes
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Current behaviour

      1. Bitbucket Mesh pods will need to run in the same cluster as the Bitbucket upstream pods.
      2. There are no Ingress rules created for Bitbucket Mesh pods and we can only use the internal service names to register Bitbucket Mesh to the upstream.

      Reference: Atlassian DC Helm Charts - Bitbucket Mesh

      Suggested solution

      Have the ability to decouple Bitbucket Mesh and Bitbucket upstream.

              Unassigned Unassigned
              mmuthusamy Moga
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: