- Add Kubernetes ingress, service for the payment observer as a stand-alone service.
- Requires update to helm chart values overrides. (See sample values)
- Some important points about the sample values.
- The
apsigningseed
is a sampel value and should be replaced with your secret configmap name.
volumeMounts:
secrets:
- name: apsigningseed
mountPath: signingseed
configMaps:
- name: assets
mountPath: assets
- New helm value overrides are required to run the payment observer as a separate service.
- Replace
observer.your_anchor_domain.com
with your valid host name.
#
# If you want to have a dedicated stellar-observer service, you need to
# uncomment the `stellarObserver` section below.
#
# Attention! If you use the stellar observer as a separate service – by setting
# `stellarObserver.enabled` flag to `true` – you must use a shared database that
# will be accessible by both deployments (sep-server and stellar-observer).
# In-memory databases won't work.
stellarObserver:
# This will enable the stellar-observer service as a separate deployment:
enabled: true
# The stellarObserver.deployment section is optional, the templates have
# default values.
deployment:
port: 8083
probePath: "/health"
probePeriodSeconds: 15
initialDelaySeconds: 60
startupProbeFailureThreshold: 10
livenessProbeFailureThreshold: 2
ingress:
tls:
host: "observer.your_anchor_domain.com" # Replace this with a valid host name
rules:
hosts:
- host: "observer.your_anchor_domain.com" # Replace this with a valid host name
path: /
pathType: Prefix