Later: Chart edits need the owner's explicit exception, and nothing in src reads a FORGE_JOB_* lane yet.
From closed pull #2124 (#1423). juniper's three reviews found the following. The chart did not connect to the code: nothing in src reads FORGE_JOB_*, and the NetworkPolicy selected a label the Job pods do not carry. docs/CLUSTER.md named a variable the chart no longer set. The helm render tests skip without helm. And chart edits need an owner exception.
Done looks like: the owner grants the exception on this issue. Then one pull adds the ServiceAccount, Role and RoleBinding, and a NetworkPolicy that selects the label the forge's Job pods actually carry. It sets only env that src reads, and docs/CLUSTER.md checks that env. The pull shows a rendered helm template result.
Later: Chart edits need the owner's explicit exception, and nothing in src reads a FORGE_JOB_* lane yet.
From closed pull #2124 (#1423). juniper's three reviews found the following. The chart did not connect to the code: nothing in
srcreadsFORGE_JOB_*, and the NetworkPolicy selected a label the Job pods do not carry. docs/CLUSTER.md named a variable the chart no longer set. The helm render tests skip without helm. And chart edits need an owner exception.Done looks like: the owner grants the exception on this issue. Then one pull adds the ServiceAccount, Role and RoleBinding, and a NetworkPolicy that selects the label the forge's Job pods actually carry. It sets only env that
srcreads, and docs/CLUSTER.md checks that env. The pull shows a renderedhelm templateresult.