image:
  repository: bitnamilegacy/mlflow

gitImage:
  repository: bitnamilegacy/git

waitContainer:
  image:
    repository: bitnamilegacy/os-shell
tracking:
  auth:
    enabled: false
  service:
    type: ClusterIP
  ingress:
    enabled: true
    pathType: ImplementationSpecific
    hostname: mlflow.example.org
    # airflow/superset과 동일하게 실측된 문제 — ingressClassName 미지정 시 이 클러스터의
    # apisix가 아예 인식하지 않아 CLASS: <none>으로 뜨고 접근이 불가능하다. path도 exact "/"
    # 만 매치되면 앱 내부 리다이렉트 이후 전부 404가 나므로 regex로 바꾼다.
    ingressClassName: "apisix"
    annotations:
      # cert-manager 사용시 인증서 자동 생성
      cert-manager.io/cluster-issuer: "selfsigned-issuer"
      cert-manager.io/duration: 8760h
      cert-manager.io/renew-before: 720h
      k8s.apisix.apache.org/use-regex: "true"
      k8s.apisix.apache.org/ssl-redirect: "true"
    path: /.*
    tls: false
    extraTls:
    - hosts:
        - mlflow.example.org
      secretName: mlflow-tls-secret
  extraArgs:
    - "--gunicorn-opts=--timeout 600"
  resources:
    limits:
      cpu: 1000m
      memory: 2Gi
    requests:
      cpu: 500m
      memory: 1Gi
run:
  resources:
    limits:
      cpu: 500m
      memory: 1Gi
    requests:
      cpu: 250m
      memory: 512Mi
  
# 내장 bitnami postgresql 서브차트 대신 cnpg-cluster(전용 인스턴스)를 외부 DB로 사용한다.
# 사전 배포: helm install mlflow-db manifests/helm/cnpg-cluster/1.0.0 \
#   -f manifests/helm/cnpg-cluster/1.0.0/custom-values.yaml \
#   -f manifests/applicationset/mlflow/2.1.0/mlflow-db-values.yaml -n <ns>
postgresql:
  enabled: false

externalDatabase:
  dialectDriver: "postgresql"
  host: "mlflow-db-rw"
  port: 5432
  user: mlflow
  password: mlflow1234
  database: mlflow
minio:
  enabled: true
  auth:
    rootUser: admin
    rootPassword: admin1234
  image:
    repository: bitnamilegacy/minio
  reousrces:
    limits:
      cpu: 500m
      memory: 1Gi
    requests:
      cpu: 250m
      memory: 512Mi