Files
harmony/examples/okd_add_node/env.sh
Sylvain Tremblay a906a51ef6 refactor(okd): rename AddOkdNodeScore to OKDAddNodeScore
Aligns with the rest of the OKD score namespace (OKDSetup01InventoryScore,
OKDBootstrap02…, OKDLoadBalancerScore, …). The Add prefix made this one
the odd name out. Renames the companion interpret (AddOkdNodeInterpret →
OKDAddNodeInterpret), the Score::name() debug string, and the
InterpretName::Custom tag for symmetry. AddNodeRole stays as-is (not a
Score, and its prefix still reads fine).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-21 15:41:40 -04:00

10 lines
416 B
Bash

export HARMONY_SECRET_NAMESPACE=okd-add-node
export HARMONY_SECRET_STORE=file
export HARMONY_DATABASE_URL=sqlite://okd_add_node.sqlite
export RUST_LOG=harmony=debug
# Required: the kubeconfig for the running OKD cluster. OKDAddNodeScore reads
# the existing nodes of the target role and pulls the user-data-managed secret
# from `openshift-machine-api` through this.
# export KUBECONFIG=/path/to/cluster/kubeconfig