archived the channel

error while upgrading version from helm chart

Aside from rolling my own github pages type of solution, is there a place to publish non-OCI helm charts for free/FOSS?

can anyone help me with this question?

https://stackoverflow.com/questions/75488507/passing-values-to-include-function-inside-range-using-defaults-with-merge

i'm struggling here.

hi - what's the difference between using sources and dependencies in the charts.yaml?
In a few examples i see folks create new charts via helm create but instead of using sources to reference an external chart they use dependencies (which doesn't seem right in my mind)

Hello, does anyone know if there is a way to run some kubectl commands that would compare a deployed helm version running in GKE on your cluster with a values.yaml to lets say the latest released helm chart (external helm chart e.g. prometheus)?

Hey guys,
How to pull dependency helm chart which is in a private repo from umbrella helm chart? [how do i pass the creds of my private chart repo to umbrella chart to pull the dependency chart]

Where does Capabilities.KubeVersion.Version come from?
In the docs it says provides information about what capabilities the Kubernetes cluster supports
Which cluster?
If I print out the variable in one of my templates it says 1.23 but I have no 1.23 k8s version installed anywhere.

Hello everyone! I have been following the CloudPosse tutorial for building the Terraform configuration of EKS and I am not being able to download any of the charts that I need to use. I am looking for making use of the external-dns one, but it throws me an error saying that it can’t find it.

I have tried the bitnami chart, the kubernetes sigstore one and now trying to move forward with the aws-load-balancer controller I can’t seem to use that chart either. I was wondering if anyone else encountered this issue? My modules look similar to this one:

module "helm_release" {
  source  = "cloudposse/helm-release/aws"
  
  # Cloud Posse recommends pinning every module to a specific version
  # version = "x.x.x"
  
  eks_cluster_oidc_issuer_url = module.eks_cluster.eks_cluster_identity_oidc_issuer
  name          = "external-dns"
  repository    = "<https://kubernetes-sigs.github.io/external-dns/>"
  chart         = "external-dns"

  create_namespace     = true
  kubernetes_namespace = "echo"

  atomic          = true
  cleanup_on_fail = true
  timeout         = 300
  wait            = true

  # Enable the IAM role
  iam_role_enabled = true

  # Add the IAM role using set()
  service_account_role_arn_annotation_enabled = true

...
}

Apologies in advance if the syntax of the module is not the best, I am learning how to use Terraform.

Hey guys
Does anyone knows how can i export all possible values to a values.yaml file from an existing chart i have locally on my machine?

Hello - Any one using kube-prometheus-stack with AWS managed Prometheus ?
Im looking for help on this issue https://github.com/prometheus-community/helm-charts/issues/2220

Does anyone know of an alternative thats like Infracost for Helm charts?

Working on drafting a Helm chart from scratch, my first ever, and could use a sounding board for suggestions and ideas on situation I'm seeing.
I currently have an initContainer that launches and executes DB migration/init steps which is fine if replicas: 1 is set but if I increase it as I would expect in a non-dev mode the initContainer pod going into a locked state as the DB isn't exclusive so I really need to find a way to execute the migration/init stageas a pod without using it as an initContainer and have the main container for the deployment hold until the migration/init pod has completed and terminated. I think this is also why my helm upgrade hangs as it launches the new deployment which hangs on the init process.

Seems to be an intermittent issue, a retry seems to be the current workaround.

And they're working on it, just found this github issue:
https://github.com/bitnami/charts/issues/8433

Bitnami chart repo appear to be broken:

$ curl -Ss <https://charts.bitnami.com/bitnami> | xmllint --format /dev/stdin
<?xml version="1.0" encoding="UTF-8"?>
<Error>
  <Code>AccessDenied</Code>
  <Message>Access Denied</Message>
  <RequestId>3JJ1S8D309MNZNFT</RequestId>
  <HostId>JD7bxIL1yZW9N+OX4yl5JWgcL6e1TR9TMGWY2YEVYUYor2mwM8EJw9XXTS1GH8hwAY2L/Begmhc=</HostId>
</Error>

Hi Does anyone know how to enable Sigv4 auth in grafana on Prom Kube Stack using helm -
I m trying to use it with aws managed Prometheus service.
Issue https://github.com/prometheus-community/helm-charts/issues/2092

Hi, I'm puzzled and hopefully someone can point me in the right direction.

The helm secret differs from the action k8s resources, which are also in line with the local values and manifest. The weird thing is that a helm(file) diff has no diff. A helm(file) apply has no changes.
API deprication tools like kubent or pluto check the helm manifest and still detect the old version '1'.

To be more clear,
• helm template > resources version "2"
• kubectl get resources -oyaml > resources version "2"
• helm get manifest > resources version "1"
• helm diff > no changes
• helm upgrade > no changes
Anyone who can point me to a solution to get everything in sync, or on how I ended up here?

Hello,

helm question here. I am migrating my library charts to ghcr.io, so I have to update references in my helm files from file://../library_charts to <oci://ghcr.io/my_org/library_charts>

So now whenever I run helm repo update, the index file gets generated with file:// URIs, instead of the new oci:// URIs.

Where does helm get the URI information from so I can update that source as well and have it point to the oci:// URI?

Hi,
I want to check if there is an helm3 chart for coreos etcd operator?

Hello Helm people. I was hoping someone could tell me what the data-loss concerns are around Helm managing CRDs? Does anyone have links to some of the discussions that took place on the matter? From the docs There is no support at this time for upgrading or deleting CRDs using Helm. This was an explicit decision after much community discussion due to the danger for unintentional data loss

Anyone using https://github.com/airflow-helm/charts/ to install airflow? Despite having specified postgres as the db to use and verifying that env vars are being set correctly, my pods are crashing with airflow.exceptions.AirflowConfigException: error: cannot use sqlite with the CeleryExecutor

I can't figure out why it's trying to use sqlite when I've specified postgres as the db to use. Any ideas?

Hi Everyone!
Is anyone using porter.sh in prod?
Specifically as a bridge between terraform and helm?

Using cloudposse’s monochart, I’m trying to populate deployment env values from both Values.env and Values.envFromFieldRefFieldPath, but it’s rendering two separate env values in the chart. when I install the chart, only one of those env values ends up in the deployment.
is it the case that line 68 here should be removed? https://github.com/cloudposse/charts/blob/master/incubator/monochart/templates/_helpers.tpl#L57-L75

The --debug flag should show you the bad yaml.

I'm not sure how to get this to work:

{{- if .Values.script.enabled -}}
apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ include "dgraph-lambda.fullname" . }}-config
  labels:
    {{- include "dgraph-lambda.labels" . | nindent 4 }}
data:
  script.js: {{ .Values.script.script }}
{{- end -}}

This get me:

[ERROR] templates/config.yaml: unable to parse YAML: error converting YAML to JSON: yaml: line 13: mapping values are not allowed in this context

And it was... grrr... this is such a frustrating part of helm, makes it so painful to debug.

Is there a way to see the badly rendered values, so I can see where I made the mistake?

Error: YAML parse error on dgraph-lambda/templates/deployment.yaml: error converting YAML to JSON: yaml: line 34: did not find expected key
helm.go:81: [debug] error converting YAML to JSON: yaml: line 34: did not find expected key
YAML parse error on dgraph-lambda/templates/deployment.yaml
...

Doesn't help. I want to see how it was rendered so that I know how to fix it. Sometimes it's just a matter of indentation.

We have a 3rd party helm chart that we are working with. it is an umbrella chart that has other umbrella charts. Probably like 3 levels of charts...many of the settings from the subcharts are not exposed in the root values.yaml. Was looking for a tool/script that will generate a values.yaml with all the values from subcharts

I'm trying to read an HTML file in and include it in a string as an annotation but having a difficult time due to what I assume is quotes/single quotes. Anyone done this before? Basically I'm including a static maintenance page as a ALB rule

As @Erik Osterman (Cloud Posse) suggested, not sure if anyone has any experience with this ->https://sweetops.slack.com/archives/CQCDCLA1M/p1607475676220800

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.

We’ve started experiencing

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 peer

quite often recently. Probably it’s due to the fact that after the deprecation many people switched to their repos

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 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/v1

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?

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)

Is there any way to get the pre-rendered YAML and/or rendered JSON, as these are troubling to debug.

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:1357

It's like What key? What was the YAML going into JSON? Staring at chart for hours, cannot spot issue.

https://helm.sh/blog/helm-turns-five/ — GitHub to take over hosting Helm stable and incubator.

We though about using helm cause of ease of install and configuration from the client side, any easy alternatives?

Hi! Me and my team are working at packaging out app into several helm charts linked with an umbrella chart. We have several services depending on others and need to pass secrets and values between them. The only ways we found was using global variables or common naming convention. Do you see any other ways that could ease this values sharing? Also we would like to avoid duplicating all the values, any insights? Thanks!

helm has broken idempotence  in versions 3.3.2 and 3.3.3.
Thus you cannot use helmfile with those versions.

Any clever ways that folks get around the fact that Helm’s lookup function won’t access the cluster during an install / upgrade --dry-run?

Keep in mind that Helm is not supposed to contact the Kubernetes API Server during a helm template or a helm install|update|delete|rollback --dry-run, so the lookup function will return nil in such a case.

This makes it so trying to dry-run my templates locally is a no go and even breaks helm lint which sucks. Anything I can do there or do I just have to live with that limitation?

@natalie has joined the channel

@Jonathan Tobe has joined the channel

Does anybody know of a useful NOTES.txt file out there? The scaffold NOTES.txt is just noise to me, but I could see others coming up with some possibly useful information to stick in there. Quick google search didn’t turn up anything however.

found a handy blog. if anyone else has the question: https://www.arthurkoziel.com/private-helm-repo-with-gcs-and-github-actions/

hi All! hope you are all well, I’ve just setup a gcs helm repo, access is currently open, have anyone set anything up where the bucket is private and you pass something for the helm repo add cmd ?

Anyone using helm-diff and/or helmfile with stable/prometheus-operator chart's additionalPrometheusRules, mind testing/reviewing https://github.com/databus23/helm-diff/pull/232?

I believe you've been affected by https://github.com/databus23/helm-diff/issues/201, which is finally being fixed by the PR.

Does anyone have a hack for cleaning up old configmaps before I hack something together?

➜  helmfile git:(master) ✗ kubectl -n kube-system get cm | wc -l
   12766

@Somnath has joined the channel