# Meerkat, community edition, one gateway on its own volume.
#
#   helm repo add meerkat https://meerkat.softwarity.dev/deploy
#   helm install meerkat meerkat/meerkat -f https://meerkat.softwarity.dev/deploy/values-ce-one-node.yaml \
#     --set admin.password='choose-one'
#
# This IS the default shape, written out so it can be read: one pod, the
# embedded store on a ReadWriteOnce volume, no database to run beside it. It
# carries a whole application - routing, accounts, roles, the built-in pages,
# TLS, the vault, the audit trail - for one organisation.
#
# What it does not do is survive the loss of its node, because a volume does
# not follow a pod from one machine to another. When that matters, go to
# values-ee-cluster.yaml.
image:
  repository: docker.io/softwarity/meerkat
  # Pin a release rather than following latest on what holds your front door.
  tag: ""

replicaCount: 1

# Set it on the command line instead of here: a password in a file is a
# password in git. Read once, on the first start, to create the first admin.
admin:
  password: ""

persistence:
  enabled: true
  size: 2Gi
  # Name your class, or let the cluster's default answer.
  storageClass: ""

service:
  type: ClusterIP
  appPort: 8080
  adminPort: 9090

# The authorities the cluster publishes, found by Domains & TLS, Trusted
# authorities, From the cluster: what signs the services a route in HTTPS
# calls. cert-manager: list the issuers, and learn one's certificate from a
# throwaway Certificate (<release>-meerkat-trust-probe, deleted at once) -
# never from the issuer's Secret, which holds its key. trust-manager: list the
# Bundles and read their ConfigMap in this namespace. On by default; false
# leaves the certificate to import by hand.
trustDiscovery:
  certManager: true
  trustManager: true