kbrew info goes parses through the recipe YAML, evaluating the Go templates.
For an execution where there kubectl context is not configured or invalid - kbrew info will fail in case where a Go template does a query to a cluster using the Helm lookup function.
This should be avoided - the user should be shown the recipe as they are. And the info command shouldn't have an independence on a cluster.
kbrew infogoes parses through the recipe YAML, evaluating the Go templates.For an execution where there kubectl context is not configured or invalid -
kbrew infowill fail in case where a Go template does a query to a cluster using the Helm lookup function.This should be avoided - the user should be shown the recipe as they are. And the
infocommand shouldn't have an independence on a cluster.