-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not specify name for HELM v3 releases #88
Comments
My bad Release Names were removed from Helm3 Not a bug, removing |
Reopen, there is still need an opportunity to specify name for the releases, eg: # For Helm 2
helm install --namespace <NAMESPACE> --name gitlab-runner -f <CONFIG_VALUES_FILE> gitlab/gitlab-runner
# For Helm 3
helm install --namespace <NAMESPACE> gitlab-runner -f <CONFIG_VALUES_FILE> gitlab/gitlab-runner from here |
Good workaround is to use example component: local env = { name: std.extVar('qbec.io/env'), namespace: std.extVar('qbec.io/defaultNs') };
local p = import '../params.libsonnet';
local params = p.components.gitlabRunner;
std.native('expandHelmTemplate')(
'../vendor/gitlab-runner',
params.values,
{
nameTemplate: params.name,
namespace: env.namespace,
thisFile: std.thisFile,
verbose: true,
}
) and values: {
components: {
gitlabRunner: {
name: 'gitlab-runner',
values: {
gitlabUrl: 'https://gitlab.exmple.org/',
runnerRegistrationToken: 'Aim3veFeuQueey6aicee',
rbac: {
create: true,
},
},
},
},
} |
helm 3 moved the name option to the main command as in |
@harsimranmaan how about using |
That might solve problem from both worlds. Maybe we can drop the --name or NAME parameter when we end support for helm2. A note in documentation about this behaviour should be enough in that case. |
The text was updated successfully, but these errors were encountered: