Have separate Values.affinity in DC helm charts for Confluence and Synchrony pods

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Done
    • None
    • Affects Version/s: None
    • Component/s: Environment - Kubernetes
    • None

      Summary

      Have separate Values.affinity in DC helm charts for Confluence and Synchrony pods

      Current behavior:

      Values.affinity in Confluence DC helm charts is currently common for Confluence and Synchrony statefulsets as seen in the screenshot.

      Suggestion

      It will be beneficial to have Values.affinity separate for Confluence and Synchrony statefulset which will help to set different affinity so that pods can be scheduled on different nodes.

        1. Screenshot 2025-01-07 at 15.22.09.png
          40 kB
          Ojas Potdar

            Assignee:
            Yevhen
            Reporter:
            Ojas Potdar (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: