Summary
Namespace is currently controlled via the NAMESPACE env var (defaulting to team1). Scripts should also accept a --namespace CLI flag so callers can specify it inline without prefixing every invocation with an env var assignment.
Affected scripts
deploy-agent.shdeploy-benchmark.shdeploy-and-evaluate.shevaluate-benchmark.sh
Proposed behaviour
- Add
--namespace NAMESPACE to each script's argument parser.
- CLI flag takes precedence over the env var; env var takes precedence over the hardcoded default (
team1).
- Pass
--namespace through in wrapper scripts (deploy-and-evaluate.sh) the same way other flags are forwarded.
Motivation
Running parallel experiments in different namespaces (e.g. team2) currently requires either editing scripts or prepending NAMESPACE=team2 to every call. A --namespace flag makes this composable with other flags and easier to use in scripts and CI.
Related: #38 (OCP runner hardening), noted in PR #33 review by @kellyaa.
Summary
Namespace is currently controlled via the
NAMESPACEenv var (defaulting toteam1). Scripts should also accept a--namespaceCLI flag so callers can specify it inline without prefixing every invocation with an env var assignment.Affected scripts
deploy-agent.shdeploy-benchmark.shdeploy-and-evaluate.shevaluate-benchmark.shProposed behaviour
--namespace NAMESPACEto each script's argument parser.team1).--namespacethrough in wrapper scripts (deploy-and-evaluate.sh) the same way other flags are forwarded.Motivation
Running parallel experiments in different namespaces (e.g.
team2) currently requires either editing scripts or prependingNAMESPACE=team2to every call. A--namespaceflag makes this composable with other flags and easier to use in scripts and CI.Related: #38 (OCP runner hardening), noted in PR #33 review by @kellyaa.