-
Notifications
You must be signed in to change notification settings - Fork 223
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
Unable to use "ct install" command #101
Comments
Your configuration is not correct. The flag |
@unguiculus Thank you for reply! |
Of course, you can test your own chart. Please familiarize yourself with |
@unguiculus Thank you. I'll definitely should reread docs and today I'll try again! |
Is this a request for help?: No
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
Version of Helm and Kubernetes:
kubectl:
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T10:39:04Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:25:46Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
helm
Client: &version.Version{SemVer:"v2.12.2", GitCommit:"7d2b0c73d734f6586ed222a567c5d103fed435be", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
ct:
Version: v2.2.0
Git commit: 00f3726
Date: 2019-01-23T14:30:52Z
License: Apache 2.0
What happened:
I was trying to use official docker container which has a tag: v2.2.0 with own made chart.
During install phase
ct
generates random release name which is not valid for helmError message:
Installing charts...
Version increment checking disabled.
Configuration
Remote: upstream
TargetBranch: master
BuildId:
LintConf: /etc/ct/lintconf.yaml
ChartYamlSchema: chart_schema.yaml
ValidateMaintainers: false
ValidateChartSchema: false
ValidateYaml: false
CheckVersionIncrement: false
ProcessAllCharts: false
Charts: [./]
ChartRepos: []
ChartDirs: [stable incubator]
ExcludedCharts: []
HelmExtraArgs: --timeout 500 --tiller-namespace kube-system --dry-run --debug
HelmRepoExtraArgs: []
Debug: true
Namespace: kube-system
ReleaseLabel: test
Charts to be processed:
./
helm init --client-only
$HELM_HOME has been configured at /root/.helm.
Not installing Tiller due to 'client-only' flag having been set
Happy Helming!
helm dependency build ./
No requirements found in .//charts.
Installing chart './'...
helm install ./ --name .-2cnt7c1osa --namespace kube-system --wait --timeout 500 --tiller-namespace kube-system --dry-run --debug
[debug] Created tunnel using local port: '39759'
[debug] SERVER: "127.0.0.1:39759"
[debug] Original chart version: ""
[debug] CHART PATH: /service-monitors
Error: release name .-2cnt7c1osa is not a valid DNS label: a DNS-1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name', or '123-abc', regex used for validation is 'a-z0-9?')
kubectl get pods --no-headers --namespace kube-system --selector test=.-2cnt7c1osa --output jsonpath={.items[*].metadata.name}
Error printing logs: Error running process: exit status 1
Deleting release '.-2cnt7c1osa'...
helm delete --purge .-2cnt7c1osa --timeout 500 --tiller-namespace kube-system --dry-run --debug
[debug] Created tunnel using local port: '45833'
[debug] SERVER: "127.0.0.1:45833"
Error: incompatible versions client[v2.12.2] server[v2.11.0]
Error deleting Helm release: Error waiting for process: exit status 1
Error installing charts: Error processing charts
✖︎ ./ > Error waiting for process: exit status 1
What you expected to happen:
Perform lint and install operations without errors
How to reproduce it (as minimally and precisely as possible):
quay.io/helmpack/chart-testing:v2.2.0
ct install --debug --charts ./ --release-label=test --helm-extra-args=" --timeout 500 --tiller-namespace kube-system --dry-run --debug" --namespace kube-system
Anything else we need to know:
The text was updated successfully, but these errors were encountered: