Have you searched for this feature request?
Problem Statement
Current implementation relies on config.yaml file in repository root directory. Which has limitations on creating multiple clusters and have multiple config file per cluster.
The secrets created for the cluster also uses the static config file path and prefix for secret creation.
Possible Solution
Allow passing config file path when executing scripts as follows:
scripts/create-cluster.sh my/path/to/config.yaml
scripts/create-config-secret.sh my/path/to/config.yaml
scripts/install.sh my/path/to/config.yaml
If the path is not supplied use the default path $REPO_ROOT/config.yaml.
Alternatives Considered
No response
Have you searched for this feature request?
Problem Statement
Current implementation relies on
config.yamlfile in repository root directory. Which has limitations on creating multiple clusters and have multiple config file per cluster.The secrets created for the cluster also uses the static config file path and prefix for secret creation.
Possible Solution
Allow passing config file path when executing scripts as follows:
If the path is not supplied use the default path
$REPO_ROOT/config.yaml.Alternatives Considered
No response