Monero Node

Abstract

Monero Node Helm Chart index.

Monero Node#

contents

meta

Installation and Upgrade#

helm upgrade --install monero oci://tccr.io/truecharts/monero-node -f values.yaml

Build Container Image#

docker build \
  --build-arg VERSION="0.0.2-$(git rev-parse --short=6 HEAD)" \
  -t ghcr.io/edwardtheharris/helm-monero-node/node:0.0.2-$(git rev-parse --short=6 HEAD) \
  -t edwardtheharris/monero-node:0.0.2-$(git rev-parse --short=6 HEAD) \
  --push -f docker/Dockerfile .

Chart#

apiVersion

API Version

The Helm API version to use for this chart.

apiVersion: v2
appVersion

App Version

This is the version number of the application being deployed. This version number should be incremented each time you make changes to the application. Versions are not expected to follow Semantic Versioning.

They should reflect the version the application is using.

It is recommended to use it with quotes.

appVersion: "0.18.3.4-2"
description

Description

A brief description of the Chart.

description: A Helm chart to deploy a Monero node to bare metal Kubernetes.
icon

Icon

A url or file path to an icon for the Chart’s application.

icon: file://./_static/img/logo/helm.png
name

Name

The name of the application or library provided by the chart.

name: monero
type

Type

A chart can be either an ‘application’ or a ‘library’ chart.

Application charts are a collection of templates that can be packaged into versioned archives to be deployed.

Library charts provide useful utilities or functions for the chart developer. They’re included as a dependency of application charts to inject those utilities and functions into the rendering pipeline. Library charts do not define any templates and therefore cannot be deployed.

type: application
version

Version

This is the chart version. This version number should be incremented each time you make changes to the chart and its templates, including the app version. Versions are expected to follow Semantic Versioning (https://semver.org/)

version: 0.0.2

Values#

autoscaling

Full Name Override

Override the release and chart name.

autoscaling:
  enabled: false
fullnameOverride: ""
image

Image Values

Describe the image to use for the node.

image:
  pullPolicy: Always
  repository: edwardtheharris/monero-node
  tag: 0.0.2
ingress

Ingress Values

Enable and configure ingress for the service.

image:
  pullPolicy: Always
  repository: edwardtheharris/monero-node
  tag: 0.0.2
labels

Labels Values

Labels to be applied to all resources

labels:
  app.kubernetes.io/node: k8s05.breeze-blocks.net
monero:
  login:
    enabled: false
    password: ''
    username: ''
nameOverride: "monero"
persistence

Image Values

Describe the image to use for the node.

persistence:
  blockchain:
    enabled: true
    mountPath: /srv/monero
    name: monero
    size: 300Gi
  storageClass: csi-lvm-linear
portal

Portal Values

Portal configuration values.

portal:
  open:
    enabled: true
securityContext

Security Context Values

Security context for the deployment’s pod.

securityContext:
  container:
    readOnlyRootFilesystem: false
    runAsGroup: 0
    runAsUser: 0
service

Service Values

Services for main and rpc ports.

service:
  enabled: true
  main:
    name: monero
    port: 18081
    protocol: TCP
    targetPort: 18081
  type: LoadBalancer
serviceAccount

Service Account Values

Enable and configure a new service account.

serviceAccount:
  annotations:
    app.kubernetes.io/name: monero
    app.kubernetes.io/instance: monero
  automount: true
  create: true
  name: monero
statefulset:
  replicas: 1

Indices and tables#

Glossary#

Docker#

Docker is the first container runtime to become ubiquitous and so is still frequently used to build images that will run on Kubernetes or other orchestrators. More information is available here.

GitHub#

Most likely the site this repository is hosted on. More information is available here.

Helm#

A tool commonly used to deploy applications to Kubernetes. More information is available here.

Kubernetes#

An ancient Greek word that means ‘sailor’ or ‘navigator’, it is the most common container orchestration system currently in use. More information is available here.

Contents