UNPKG

@hashgraph/solo

Version:

An opinionated CLI tool to deploy and manage private Hedera Networks.

286 lines (284 loc) 6.84 kB
labels: solo.hedera.com/testSuiteName: "" solo.hedera.com/testName: "" solo.hedera.com/testRunUID: "" solo.hedera.com/testCreationTimestamp: "" solo.hedera.com/testExpirationTimestamp: "" solo.hedera.com/testRequester: "" graphql: # not needed for default use case enabled: false rosetta: # not needed for default use case enabled: false redis: enabled: true # namespaceOverride: "{{ tpl (.Values.global.namespaceOverride | toString) }}" # importer is a component of the hedera mirror node # config for subchart hedera-mirror/importer importer: nodeSelector: {} tolerations: - key: "solo-scheduling.io/os" operator: "Equal" value: "linux" effect: "NoSchedule" - key: "solo-scheduling.io/role" operator: "Equal" value: "network" effect: "NoSchedule" resources: requests: cpu: 0 memory: 0 limits: cpu: 1000m memory: 2000Mi readinessProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 livenessProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 startupProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 envFrom: - secretRef: name: mirror-passwords - secretRef: name: "{{ .Release.Name }}-redis" - secretRef: name: uploader-mirror-secrets # The addressbook.bin file updates will be handled by infrastructure code or solo addressBook: "" config: # importer is a springboot app, its application.yaml configuration starts here # This config is mounted at [/usr/etc/hedera/application.yaml] in the importer pod hedera: mirror: importer: startDate: 1970-01-01T00:00:00Z network: other downloader: allowAnonymousAccess: false bucketName: "solo-streams" # for s3 configuration of mirror node look at uploader-mirror-secrets.yaml parser: record: entity: persist: pendingReward: false sidecar: enabled: true grpc: nodeSelector: {} tolerations: - key: "solo-scheduling.io/os" operator: "Equal" value: "linux" effect: "NoSchedule" - key: "solo-scheduling.io/role" operator: "Equal" value: "network" effect: "NoSchedule" resources: requests: cpu: 0 memory: 0 limits: cpu: 500m memory: 1000Mi readinessProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 livenessProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 startupProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 postgresql: persistence: size: 10Gi postgresql: nodeSelector: {} tolerations: - key: "solo-scheduling.io/os" operator: "Equal" value: "linux" effect: "NoSchedule" - key: "solo-scheduling.io/role" operator: "Equal" value: "network" effect: "NoSchedule" resources: requests: cpu: 0 memory: 0 limits: cpu: 1000m memory: 1000Mi pgpool: replicaCount: 0 rest: nodeSelector: {} tolerations: - key: "solo-scheduling.io/os" operator: "Equal" value: "linux" effect: "NoSchedule" - key: "solo-scheduling.io/role" operator: "Equal" value: "network" effect: "NoSchedule" resources: requests: cpu: 0 memory: 0 limits: cpu: 500m memory: 500Mi readinessProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 livenessProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 startupProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 monitor: enabled: false redis: enabled: true global: hostname: "localhost" restjava: nodeSelector: {} tolerations: - key: "solo-scheduling.io/os" operator: "Equal" value: "linux" effect: "NoSchedule" - key: "solo-scheduling.io/role" operator: "Equal" value: "network" effect: "NoSchedule" resources: requests: cpu: 0 memory: 0 limits: cpu: 500m memory: 500Mi readinessProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 livenessProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 startupProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 web3: nodeSelector: {} tolerations: - key: "solo-scheduling.io/os" operator: "Equal" value: "linux" effect: "NoSchedule" - key: "solo-scheduling.io/role" operator: "Equal" value: "network" effect: "NoSchedule" resources: requests: cpu: 0 memory: 0 limits: cpu: 1000m memory: 1000Mi readinessProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 livenessProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 startupProbe: initialDelaySeconds: 0 periodSeconds: 1 failureThreshold: 60 # 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: "solo-scheduling.io/os" operator: "Equal" value: "linux" effect: "NoSchedule" - key: "solo-scheduling.io/role" operator: "Equal" value: "network" effect: "NoSchedule" resources: requests: cpu: 0 memory: 0 limits: cpu: 500m memory: 1000Mi envFrom: - secretRef: name: mirror-passwords - secretRef: name: "{{ .Release.Name }}-redis" - secretRef: name: uploader-mirror-secrets config: hedera: mirror: common: realm: 0 shard: 0 monitor: publish: scenarios: pinger: properties: amount: 1 maxTransactionFee: 10000 senderAccountId: 0.0.2 recipientAccountId: 0.0.55 transferTypes: - CRYPTO receiptPercent: 1 tps: 0 type: CRYPTO_TRANSFER subscribe: grpc: hcs: enabled: false rest: transactionId: enabled: true samplePercent: 1 network: OTHER readinessProbe: failureThreshold: 60 initialDelaySeconds: 0 timeoutSeconds: 1