• 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.

      Issue Summary

      The Crowd Helm chart currently lacks a database configuration section, which is available in other products such as JIRA and Confluence.

      Confluence helm example
      # REQUIRED - Database configuration
      #
      # Confluence requires a backend database. The configuration below can be used to define the
      # database to use and its connection details.
      # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#database-connectivity
      #
      database:
      
        # -- The database type that should be used. If not specified, then it will need to be
        # provided via the browser during manual configuration post deployment. Valid values
        # include:
         # * 'postgresql'
         # * 'mysql'
         # * 'oracle'
         # * 'mssql'
        # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#databasetype
        #
        type:
      
        # -- The jdbc URL of the database. If not specified, then it will need to be provided
        # via the browser during manual configuration post deployment. Example URLs include:
         # * 'jdbc:postgresql://<dbhost>:5432/<dbname>'
         # * 'jdbc:mysql://<dbhost>/<dbname>'
         # * 'jdbc:sqlserver://<dbhost>:1433;databaseName=<dbname>'
         # * 'jdbc:oracle:thin:@<dbhost>:1521:<SID>'
        # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#databaseurl
        #
        url:
      
        # JDBC connection credentials
        #
        credentials:
      
          # -- The name of the K8s Secret that contains the database login credentials.
          # If the secret is specified, then the credentials will be automatically utilised on
          # Confluence startup. If the secret is not provided, then the credentials will need to be
          # provided via the browser during manual configuration post deployment.
          #
          # Example of creating a database credentials K8s secret below:
          # 'kubectl create secret generic <secret-name> --from-literal=username=<username> \
          # --from-literal=password=<password>'
          # https://kubernetes.io/docs/concepts/configuration/secret/#opaque-secrets
          #
          secretName:
      
          # -- The key ('username') in the Secret used to store the database login username
          #
          usernameSecretKey: username
      
          # -- The key ('password') in the Secret used to store the database login password
          #
          passwordSecretKey: password
      

      Why it is important

      Including a database configuration section is essential to automate the configuration process in Kubernetes, ensuring consistency and efficiency.

            [SCALE-132] Add Database Configuration Support to Crowd Helm Chart

            Lei Wang made changes -
            Labels New: kubernetes
            Lei Wang made changes -
            Description Original: h4. Issue Summary

            The Crowd Helm chart currently lacks a database configuration section, which is available in other products such as [JIRA|https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/jira/values.yaml] and [Confluence|https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/confluence/values.yaml].
            {code:java|title=Confluence helm example}
            # REQUIRED - Database configuration
            #
            # Confluence requires a backend database. The configuration below can be used to define the
            # database to use and its connection details.
            # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#database-connectivity
            #
            database:

              # -- The database type that should be used. If not specified, then it will need to be
              # provided via the browser during manual configuration post deployment. Valid values
              # include:
               # * 'postgresql'
               # * 'mysql'
               # * 'oracle'
               # * 'mssql'
              # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#databasetype
              #
              type:

              # -- The jdbc URL of the database. If not specified, then it will need to be provided
              # via the browser during manual configuration post deployment. Example URLs include:
               # * 'jdbc:postgresql://&lt;dbhost&gt;:5432/&lt;dbname&gt;&#39;
               # * 'jdbc:mysql://&lt;dbhost&gt;/&lt;dbname&gt;&#39;
               # * 'jdbc:sqlserver://&lt;dbhost&gt;:1433;databaseName=&lt;dbname&gt;&#39;
               # * 'jdbc:oracle:thin:@<dbhost>:1521:<SID>'
              # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#databaseurl
              #
              url:

              # JDBC connection credentials
              #
              credentials:

                # -- The name of the K8s Secret that contains the database login credentials.
                # If the secret is specified, then the credentials will be automatically utilised on
                # Confluence startup. If the secret is not provided, then the credentials will need to be
                # provided via the browser during manual configuration post deployment.
                #
                # Example of creating a database credentials K8s secret below:
                # 'kubectl create secret generic <secret-name> --from-literal=username=<username> \
                # --from-literal=password=<password>'
                # https://kubernetes.io/docs/concepts/configuration/secret/#opaque-secrets
                #
                secretName:

                # -- The key ('username') in the Secret used to store the database login username
                #
                usernameSecretKey: username

                # -- The key ('password') in the Secret used to store the database login password
                #
                passwordSecretKey: password
            {code}
            h4. Why it is important

            Including a database configuration section is essential to automate the configuration process in Kubernetes, ensuring consistency and efficiency.
            New: h4. Issue Summary

            The [Crowd Helm chart|https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/crowd/values.yaml] currently lacks a database configuration section, which is available in other products such as [JIRA|https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/jira/values.yaml] and [Confluence|https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/confluence/values.yaml].
            {code:java|title=Confluence helm example}
            # REQUIRED - Database configuration
            #
            # Confluence requires a backend database. The configuration below can be used to define the
            # database to use and its connection details.
            # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#database-connectivity
            #
            database:

              # -- The database type that should be used. If not specified, then it will need to be
              # provided via the browser during manual configuration post deployment. Valid values
              # include:
               # * 'postgresql'
               # * 'mysql'
               # * 'oracle'
               # * 'mssql'
              # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#databasetype
              #
              type:

              # -- The jdbc URL of the database. If not specified, then it will need to be provided
              # via the browser during manual configuration post deployment. Example URLs include:
               # * 'jdbc:postgresql://&lt;dbhost&gt;:5432/&lt;dbname&gt;&#39;
               # * 'jdbc:mysql://&lt;dbhost&gt;/&lt;dbname&gt;&#39;
               # * 'jdbc:sqlserver://&lt;dbhost&gt;:1433;databaseName=&lt;dbname&gt;&#39;
               # * 'jdbc:oracle:thin:@<dbhost>:1521:<SID>'
              # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#databaseurl
              #
              url:

              # JDBC connection credentials
              #
              credentials:

                # -- The name of the K8s Secret that contains the database login credentials.
                # If the secret is specified, then the credentials will be automatically utilised on
                # Confluence startup. If the secret is not provided, then the credentials will need to be
                # provided via the browser during manual configuration post deployment.
                #
                # Example of creating a database credentials K8s secret below:
                # 'kubectl create secret generic <secret-name> --from-literal=username=<username> \
                # --from-literal=password=<password>'
                # https://kubernetes.io/docs/concepts/configuration/secret/#opaque-secrets
                #
                secretName:

                # -- The key ('username') in the Secret used to store the database login username
                #
                usernameSecretKey: username

                # -- The key ('password') in the Secret used to store the database login password
                #
                passwordSecretKey: password
            {code}
            h4. Why it is important

            Including a database configuration section is essential to automate the configuration process in Kubernetes, ensuring consistency and efficiency.
            Lei Wang made changes -
            Description Original: h4. Issue Summary
            The Crowd Helm chart currently lacks a database configuration section, which is available in other products such as JIRA and Confluence.

            h4. Why it is important
            Including a database configuration section is essential to automate the configuration process in Kubernetes, ensuring consistency and efficiency.
            New: h4. Issue Summary

            The Crowd Helm chart currently lacks a database configuration section, which is available in other products such as [JIRA|https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/jira/values.yaml] and [Confluence|https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/confluence/values.yaml].
            {code:java|title=Confluence helm example}
            # REQUIRED - Database configuration
            #
            # Confluence requires a backend database. The configuration below can be used to define the
            # database to use and its connection details.
            # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#database-connectivity
            #
            database:

              # -- The database type that should be used. If not specified, then it will need to be
              # provided via the browser during manual configuration post deployment. Valid values
              # include:
               # * 'postgresql'
               # * 'mysql'
               # * 'oracle'
               # * 'mssql'
              # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#databasetype
              #
              type:

              # -- The jdbc URL of the database. If not specified, then it will need to be provided
              # via the browser during manual configuration post deployment. Example URLs include:
               # * 'jdbc:postgresql://&lt;dbhost&gt;:5432/&lt;dbname&gt;&#39;
               # * 'jdbc:mysql://&lt;dbhost&gt;/&lt;dbname&gt;&#39;
               # * 'jdbc:sqlserver://&lt;dbhost&gt;:1433;databaseName=&lt;dbname&gt;&#39;
               # * 'jdbc:oracle:thin:@<dbhost>:1521:<SID>'
              # https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#databaseurl
              #
              url:

              # JDBC connection credentials
              #
              credentials:

                # -- The name of the K8s Secret that contains the database login credentials.
                # If the secret is specified, then the credentials will be automatically utilised on
                # Confluence startup. If the secret is not provided, then the credentials will need to be
                # provided via the browser during manual configuration post deployment.
                #
                # Example of creating a database credentials K8s secret below:
                # 'kubectl create secret generic <secret-name> --from-literal=username=<username> \
                # --from-literal=password=<password>'
                # https://kubernetes.io/docs/concepts/configuration/secret/#opaque-secrets
                #
                secretName:

                # -- The key ('username') in the Secret used to store the database login username
                #
                usernameSecretKey: username

                # -- The key ('password') in the Secret used to store the database login password
                #
                passwordSecretKey: password
            {code}
            h4. Why it is important

            Including a database configuration section is essential to automate the configuration process in Kubernetes, ensuring consistency and efficiency.
            Lei Wang made changes -
            Affects Version/s New: master [ 89990 ]
            Lei Wang created issue -

              Unassigned Unassigned
              lwang3@atlassian.com Lei Wang
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: