reportportal:
  serviceindex:
    resources:
      requests:
        cpu: 50m
  uat:
    resources:
      requests:
        cpu: 50m
  serviceui:
    resources:
      requests:
        cpu: 50m
  serviceapi:
    resources:
      requests:
        cpu: 50m
  serviceanalyzer:
    resources:
      requests:
        cpu: 50m
  serviceanalyzertrain:
    resources:
      requests:
        cpu: 50m

  rabbitmq:
    SecretName: "reportportal-rabbitmq-creds"
    endpoint:
      address: report-portal-rabbitmq.report-portal.svc.cluster.local
      user: user
      apiuser: user

  postgresql:
    SecretName: "reportportal-postgresql-creds"
    endpoint:
      address: reportportal-primary.report-portal.svc.cluster.local

  elasticsearch:
    endpoint: opensearch-cluster-master.report-portal.svc.cluster.local:9200

  storage:
    type: minio
    secretName: "reportportal-minio-creds"
    accesskeyName: "root-user"
    secretkeyName: "root-password"
    endpoint: http://report-portal-minio.report-portal.svc.cluster.local:9000
    endpointshort: report-portal-minio.report-portal.svc.cluster.local:9000

  ingress:
    # IF YOU HAVE SOME DOMAIN NAME SET INGRESS.USEDOMAINNAME to true and redefine url
    usedomainname: true
    hosts:
      - report-portal.example.com

minio:
  auth:
    existingSecret: reportportal-minio-creds
  persistence:
    size: 1Gi

rabbitmq:
  auth:
    existingPasswordSecret: reportportal-rabbitmq-creds
    existingErlangSecret: reportportal-rabbitmq-creds
  persistence:
    size: 1Gi

opensearch:
  singleNode: true
  startupProbe:
    initialDelaySeconds: 45
  extraEnvs:
    - name: DISABLE_INSTALL_DEMO_CONFIG
      value: "true"
    - name: DISABLE_SECURITY_PLUGIN
      value: "true"
  resources:
    requests:
      cpu: "100m"
      memory: "2Gi"

  persistence:
    size: 3Gi

# Enable SAML authentication via Keycloak.
# Note: Enabling SAML authentication also requires the keycloak-operator to process Keycloak resources.
# For detailed instructions on setting up SAML authentication for report-portal, refer to:
# https://docs.kuberocketci.io/docs/operator-guide/project-management-and-reporting/reportportal-keycloak
saml:
  enabled: false

# This section enables configuration for using External Secrets Operator (ESO) as the secret manager.
# Prerequisite: Ensure that ESO is installed in the cluster.
# Refer to the EDP cluster add-on for ESO installation and setup:
# https://github.com/epam/edp-cluster-add-ons/tree/main/clusters/core/addons/external-secrets
#
# Ensure that you have created the necessary roles for ESO integration.
# Follow the detailed instructions here:
# https://docs.kuberocketci.io/docs/operator-guide/secrets-management/external-secrets-operator-integration#aws-parameter-store-scenario-in-kuberocketci
eso:
  # -- Install components of the ESO.
  enabled: true
  # -- Defines provider type. One of `aws` or `generic`.
  type: "aws"
  # -- Defines Secret Store name.
  secretStoreName: "aws-parameterstore"
  # -- Value name in AWS ParameterStore, AWS SecretsManager or other Secret Store.
  secretName: "/infra/core/addons/reportportal"
  # -- Role ARN for the ExternalSecretOperator to assume.
  roleArn: arn:aws:iam::012345678910:role/AWSIRSA_Shared_ExternalSecretOperatorAccess
  # Defines Secret Store configuration. Used when eso.type is set to "generic".
  generic:
    secretStore:
      # -- Defines SecretStore provider configuration.
      providerConfig: {}
      #  gcpsm:
      #    projectID: "alphabet-123"
