Package Details: kubernetes-helm2 2.17.0-1

Git Clone URL: https://aur.archlinux.org/kubernetes-helm2.git (read-only, click to copy)
Package Base: kubernetes-helm2
Description: A tool to manage Kubernetes charts
Upstream URL: https://github.com/helm/helm
Keywords: helm kubernetes
Licenses: Apache
Submitter: tongpu
Maintainer: tongpu (eyenx)
Last Packager: tongpu
Votes: 3
Popularity: 0.075047
First Submitted: 2019-11-18 20:43
Last Updated: 2020-10-28 08:48

Latest Comments

1 2 Next › Last »

tongpu commented on 2020-06-12 18:13

Had the same issue during my build when upgrading. Clearing the glide cache using glide cc fixed it for me.

navarrothiago commented on 2020-06-12 18:03

Does anyone faced the error below for kubernetes-helm2 2.16.8-1? [INFO] --> Fetching updates for google.golang.org/genproto [ERROR] Update failed for google.golang.org/genproto: The Remote does not match the VCS endpoint [ERROR] Update failed for cloud.google.com/go: The Remote does not match the VCS endpoint [ERROR] Failed to install: The Remote does not match the VCS endpoint The Remote does not match the VCS endpoint

intelfx commented on 2020-04-21 08:06

+1 for renaming the binary. Same rationale as with python2 -> python3. The old one is "legacy" and close to being EOLd, but still widely used alongside the new one.

j3j5 commented on 2020-03-25 09:59

+1 from me on renaming the binary to helm2, that way we can have both living on the same system.

tongpu commented on 2020-01-24 17:30

@nullnan: I'll create a new package release with a note to provide feedback if we should use helm or helm2 as the binary name. Without any feedback it's rather hard to guess how many setups we're going to break. We already have enough kubernetes-helm packages in AUR, so I'm not going to create another one. ;)

nullnan commented on 2020-01-23 00:00

@tongpu:

Would you be so kind to create another package then that attends to the "issue" that @tensor5 brought up instead?

I also would be glad if I could use this together with Helm v3 as /helm (v3) and /helm2 (v2).

E.g. the GitLab Helm Chart is still not compatible with Helm v3 - even though they finally fixed their issues with K8s 16.x as of "today" - and in this case no conflicts would pop up with the existing Helm v3 AUR pkgs, I would guess. One would need to implement the Tiller scripts for K8s again, though.

Like:

kubectl create serviceaccount --namespace kube-system tiller && kubectl create clusterrolebinding tiller-clusterrolebinding --clusterrole cluster-admin --serviceaccount kube-system:tiller && helm2 init --service-account tiller --wait

Thanks for your reply in advance :)

tongpu commented on 2020-01-21 17:58

@NeoMorfeo: I just built the package on my machine without issues. Could you try of clearing the glide cache resolves the issue for you: glide cache-clear

tongpu commented on 2020-01-21 17:57

@tensor5: My idea for this package was to provide people with a new package to keep being updated with Helm 2 releases. As I can't estimate the user base of this package and it would be a breaking change I'm currently not considering to rename the binary included in this package.

NeoMorfeo commented on 2020-01-21 08:35

There was an error on a clean install... can you please check?

''' INFO] Removing: /home/neomorfeo/.cache/pikaur/build/kubernetes-helm2/src/src/k8s.io/helm/vendor/sigs.k8s.io/kustomize/vendor go build -o bin/protoc-gen-go ./vendor/github.com/golang/protobuf/protoc-gen-go go: cannot find main module, but found glide.lock in /home/neomorfeo/.cache/pikaur/build/kubernetes-helm2/src/src/k8s.io/helm to create a module there, run: go mod init make: *** [Makefile:176: bootstrap] Error 1 ==> ERROR: '''

tensor5 commented on 2019-12-26 06:53

Could you rename the binary /usr/bin/helm to /usr/bin/helm2? This way it would be possible to install it side by side with kubernetes-helm v3.