helmArchived
5 messages
Archive: https://archive.sweetops.com/helm/
Joaquin Menchacaover 5 years ago(edited)
Is there any way to get the pre-rendered YAML and/or rendered JSON, as these are troubling to debug.
It's like What key? What was the YAML going into JSON? Staring at chart for hours, cannot spot issue.
Error: YAML parse error on dgraph/templates/zero/svc.yaml: error converting YAML to JSON: yaml: line 15: did not find expected key
helm.go:84: [debug] error converting YAML to JSON: yaml: line 15: did not find expected key
YAML parse error on dgraph/templates/zero/svc.yaml
<http://helm.sh/helm/v3/pkg/releaseutil.(*manifestFile).sort|helm.sh/helm/v3/pkg/releaseutil.(*manifestFile).sort>
/home/circleci/helm.sh/helm/pkg/releaseutil/manifest_sorter.go:146
<http://helm.sh/helm/v3/pkg/releaseutil.SortManifests|helm.sh/helm/v3/pkg/releaseutil.SortManifests>
/home/circleci/helm.sh/helm/pkg/releaseutil/manifest_sorter.go:106
<http://helm.sh/helm/v3/pkg/action.(*Configuration).renderResources|helm.sh/helm/v3/pkg/action.(*Configuration).renderResources>
/home/circleci/helm.sh/helm/pkg/action/action.go:159
<http://helm.sh/helm/v3/pkg/action.(*Install).Run|helm.sh/helm/v3/pkg/action.(*Install).Run>
/home/circleci/helm.sh/helm/pkg/action/install.go:238
main.runInstall
/home/circleci/helm.sh/helm/cmd/helm/install.go:229
main.newInstallCmd.func1
/home/circleci/helm.sh/helm/cmd/helm/install.go:117
<http://github.com/spf13/cobra.(*Command).execute|github.com/spf13/cobra.(*Command).execute>
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:842
<http://github.com/spf13/cobra.(*Command).ExecuteC|github.com/spf13/cobra.(*Command).ExecuteC>
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950
<http://github.com/spf13/cobra.(*Command).Execute|github.com/spf13/cobra.(*Command).Execute>
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887
main.main
/home/circleci/helm.sh/helm/cmd/helm/helm.go:83
runtime.main
/usr/local/go/src/runtime/proc.go:203
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1357It's like What key? What was the YAML going into JSON? Staring at chart for hours, cannot spot issue.
vroadover 5 years ago
Hi,
could you make cloudposse/prometheus-to-cloudwatch available in helm repo?
That will make keeping my chart installation up-to-date little easier.
(Moved from #general)
could you make cloudposse/prometheus-to-cloudwatch available in helm repo?
That will make keeping my chart installation up-to-date little easier.
(Moved from #general)
frochover 5 years ago(edited)
hey folks, long time fan of cloudposse, first time poster.
i’ve been digging around for an openvpn implementation to run in k8s (EKS 1.16, specifically) and stumbled upon this:
https://artifacthub.io/packages/helm/cloudposse/openvpn
it was republished on Oct 22nd, but still uses
https://artifacthub.io/packages/helm/cloudposse/route53-kubernetes
republished on Oct 22nd as well, which also uses
in addition the openvpn chart relies on a Github-PAM module to offer OAuth, which seems to no longer exist, or was possibly renamed to:
https://artifacthub.io/packages/helm/cloudposse/github-authorized-keys
itself republished on Oct 22nd
succinctly, i guess my question is: am i on a wild goose chase if i try to unravel how to use all this?
i’ve been digging around for an openvpn implementation to run in k8s (EKS 1.16, specifically) and stumbled upon this:
https://artifacthub.io/packages/helm/cloudposse/openvpn
it was republished on Oct 22nd, but still uses
extensions/v1beta1 instead of apps/v1 API versions for deployments. it also has a dependency on this chart:https://artifacthub.io/packages/helm/cloudposse/route53-kubernetes
republished on Oct 22nd as well, which also uses
extensions/v1beta1 instead of apps/v1in addition the openvpn chart relies on a Github-PAM module to offer OAuth, which seems to no longer exist, or was possibly renamed to:
https://artifacthub.io/packages/helm/cloudposse/github-authorized-keys
itself republished on Oct 22nd
succinctly, i guess my question is: am i on a wild goose chase if i try to unravel how to use all this?
Andrew Nazarovabout 5 years ago
We’ve started experiencing
quite often recently. Probably it’s due to the fact that after the deprecation many people switched to their repos
Error: looks like "<https://charts.bitnami.com/bitnami>" is not a valid chart repository or cannot be reached: read tcp x.x.x.x:59030->x.x.x.x:443: read: connection reset by peerquite often recently. Probably it’s due to the fact that after the deprecation many people switched to their repos
Tim Birkettabout 5 years ago(edited)
If you still use charts from the old Google stable repos... their new location is: https://charts.helm.sh/stable
There are many charts that are either not ported to anywhere else or the changes between the charts in stable and the charts in new repos are very large and would require some hefty re-engineering.
There are many charts that are either not ported to anywhere else or the changes between the charts in stable and the charts in new repos are very large and would require some hefty re-engineering.