--clusterdir <directory> specify the path to the cluster directory. This overrides the default of KR8_BASE/clusters
--componentdir <directory> specify the path to the component directory. This overrides the default of KR8_BASE/components
--clusterparams <filepath.jsonnet provide a jsonnet file that should contain cluster parameters. It can be combined with --cluster <clustername> to specify overrides or additional parameters to be added ahead of the parameters defined by the cluster. It can also be used separately without specifying --cluster <clustername at all.
These options are primarily meant to help with testing, but also enhance the possible ways that kr8 could be used.
In addition to this, when defining components to include in "_components", which would normally look like this:
and the components will be looked for in the component directory. The intention is to later expand clusterdir, to add multiple search locations, and probably deprecate the "path" field.
Adds three new options
--clusterdir <directory>
specify the path to the cluster directory. This overrides the default of KR8_BASE/clusters--componentdir <directory>
specify the path to the component directory. This overrides the default of KR8_BASE/components--clusterparams <filepath.jsonnet
provide a jsonnet file that should contain cluster parameters. It can be combined with--cluster <clustername>
to specify overrides or additional parameters to be added ahead of the parameters defined by the cluster. It can also be used separately without specifying--cluster <clustername
at all.These options are primarily meant to help with testing, but also enhance the possible ways that kr8 could be used.
In addition to this, when defining components to include in "_components", which would normally look like this:
can now be specified like this instead
and the components will be looked for in the component directory. The intention is to later expand clusterdir, to add multiple search locations, and probably deprecate the "path" field.