Documentation Hub
On-Premise
On-Premise
  • On-Premise Installation Manual
  • Keyless Backend Installation
    • Planning for installation
    • Components
  • Infrastructural requirements
  • Monitoring
  • Installation procedure
    • General Configuration
    • Namespace
    • Helm setup
    • Node Persistence
    • Circuit Storage
    • Core Daemon
    • Metrics Collector
    • Operations Service
    • Administrator Dashboard
  • Upgrade procedure
    • Cluster and Runtime
      • Breaking changes
        • Release 1.3.0
    • Databases
  • Checking the installation completed successfully
  • Helm and Components Versions
Powered by GitBook
On this page

Was this helpful?

  1. Installation procedure

Operations Service

To correctly set up this service the cluster’s internal endpoint is required to allow Operations Service to connect to Node Persistence. As above, the default values are usually enough, unless each service is deployed in its own dedicated namespace:

global:
  namespace: <operations-service-namespace>

image:
  tag: 2.23.0

configMap:
  # -- Node Persistence URI
  apiNodePersistenceBasePath: http://node-persistence
  # -- Core Daemon URI
  apiCoreDaemonBasePath: http://core-daemon

# -- Suggested sizing
resources:
  ## -- Limits
  limits:
    cpu: 1800m
    memory: 2048Mi
  ## -- Requests
  requests:
    cpu: 100m
    memory: 512Mi

Last updated 1 month ago

Was this helpful?