Releases: stellar/helm-charts
Anchor Platform Helm Chart Release 0.3.97 Latest
This release fixes a bug in the the Anchor Platform Helm Chart where the Stellar Observer deployment annotations were being read from the Sep Service deployment values. You can now assign Observer Deployment annotations using the following structure:
stellarObserver.deployment.annotations
for example:
stellarObserver:
enabled: true
deployment:
annotations:
prometheus.io/path: /actuator/prometheus
prometheus.io/port: "18083"
prometheus.io/scrape: "true"
Anchor Platform Helm Chart Release 0.3.96 Latest
This release updates the Anchor Platform Helmchart to pin the Stellar Observer Service Metrics Port to 18083. Previously the port was 8082. Note, the Stellar Sep Service prometheus port remains as 8082. There are not updates to helm values required for this change, however you must adjust your monitoring infrastructure.
Anchor Platform Helm Chart Release 0.3.95
- expose metrics port in observer service
- externalize helm chart values for metrics-service configuration
You can set metrics-service optionalMetricsEnabled and runInterval values under stellar/app_config/metrics_service as follows:
stellar:
app_config:
metrics_service:
enabled: true
runInterval: 60
Anchor Platform Helm Chart Release 0.3.93 Latest
helm chart - remove duplicate args field for observer
What's Changed
Full Changelog: 0.3.93...0.3.94
Anchor Platform Helm Chart Release 0.3.93 Latest
What's Changed
values.yaml file
deployment:
labels:
keya: valuea
keyb: valueb
Full Changelog: 0.3.92...0.3.93
Anchor Platform Helm Chart Release 0.3.92
- make app_config.integration-auth.authType in the config map configurable
- can be set in the values file via
app_config.app.authType
(example below) - (defaults to JWT_TOKEN if no value is specified in the values file)
- can be set in the values file via
stellar:
app_config:
app:
authType: API_KEY
What's Changed
New Contributors
Full Changelog: 0.3.91...0.3.92
Anchor Platform Helm Chart Release 0.3.91
- 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