Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add Pinger config #959

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 47 additions & 0 deletions charts/fullstack-deployment/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -386,6 +386,53 @@ hedera-mirror-node:
value: "network"
effect: "NoSchedule"

# config for subchart hedera-mirror/monitor
# Sets up a Pinger service that periodically submits CRYPTO_TRANSFER transactions
# Additional configuration for node addresses, operator id and key should be handled by infrastructure code or solo
monitor:
nodeSelector: {}
tolerations:
- key: "fullstack-scheduling.io/os"
operator: "Equal"
value: "linux"
effect: "NoSchedule"
- key: "fullstack-scheduling.io/role"
operator: "Equal"
value: "network"
effect: "NoSchedule"
envFrom:
- secretRef:
name: mirror-passwords
- secretRef:
name: "{{ .Release.Name }}-redis"
- secretRef:
name: uploader-mirror-secrets
config:
hedera:
mirror:
monitor:
publish:
scenarios:
pinger:
properties:
amount: 1
maxTransactionFee: 10000
senderAccountId: 0.0.2
recipientAccountId: 0.0.55
transferTypes:
- CRYPTO
receiptPercent: 1
tps: 10
type: CRYPTO_TRANSFER
subscribe:
grpc:
hcs:
enabled: false
rest:
transactionId:
enabled: true
samplePercent: 1
network: OTHER
haproxy-ingress:
controller:
service:
Expand Down
Loading