Files
shaandClaude Opus 5 eaa59b7361 nodered-mcp: add noderedInsecure for self-signed upstreams
Venus OS (Victron Cerbo GX) serves Node-RED on :1881 over HTTPS with a
self-signed certificate, so the server cannot reach it without waiving
verification -- it starts fine and then logs "could not detect Node-RED
version" while every tool fails. Exposes upstream's NODERED_INSECURE,
defaulted off.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-22 22:24:41 +03:00

58 lines
1.3 KiB
YAML

image:
repository: ghcr.io/fgjcarlos/nodered-mcp
pullPolicy: IfNotPresent
# The container's HTTP listener. Upstream's streamable-HTTP transport serves
# MCP at /mcp on this port.
port: 8090
service:
type: ClusterIP
port: 8090
# The Node-RED admin API this server drives, e.g. http://node-red:1880
noderedURL: ""
# Skip TLS verification against noderedURL. Needed when Node-RED is served
# over https with a self-signed certificate -- Venus OS (Victron Cerbo GX)
# does exactly that on port 1881.
noderedInsecure: false
# Refuse every write tool (flow deploy, node install). Leave on unless the
# agent is meant to change flows.
readOnly: true
# Secret holding the server's own bearer token. Upstream requires
# MCP_HTTP_TOKEN — the listener binds all interfaces, so there is no
# "trusted loopback" mode to fall back on.
existingSecret: ""
tokenKey: MCP_HTTP_TOKEN
# Additional non-secret environment variables
env: {}
# Additional secret-backed environment variables
secretEnvKeys: []
# - envName: NODERED_TOKEN
# secretKey: NODERED_TOKEN
resources:
requests:
cpu: "50m"
memory: "64Mi"
limits:
cpu: "500m"
memory: "256Mi"
nodeSelector: {}
tolerations: []
affinity: {}
ingresses: {}
# https:
# host: red-mcp.mcp.example.com
# annotations: {}
# tls:
# - hosts:
# - red-mcp.mcp.example.com