okgolove/helm-charts

Helm chart repository

helm-charts's Issues

Error: template: goldpinger/templates/daemonset.yaml:65:53: executing "goldpinger/templates/daemonset.yaml" at <eq $k.value "true">: error calling eq: incompatible types for comparison.

Hi

When using extraEnv I get a bug. My key value pairs:

  - name: USE_HOST_IP
    value: true
  - name: POD_IP
    valueFrom:
      fieldRef:
        fieldPath: status.podIP
  - name: HOSTS_TO_RESOLVE
    value: "gitlab.domain.local"
  - name: TCP_TARGETS
    value: 10.69.24.235:6443 10.69.24.236:6443 10.69.24.233:6443 10.69.24.232:6443 10.69.24.231:6443

The error is Error: template: goldpinger/templates/daemonset.yaml:65:53: executing "goldpinger/templates/daemonset.yaml" at <eq $k.value "true">: error calling eq: incompatible types for comparison.

I am using helm v3.6.3 on a k8s 1.24.10 cluster.

Thanks!

Not pull chart latest version

BUG REPORT

When installing a new cluster, I failed to download the latest version
it looks like the readme is outdated and the new version is not published as an archive

Version of Helm and Kubernetes:

Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.9", GitCommit:"4fb7ed12476d57b8437ada90b4f93b17ffaeed99", GitTreeState:"clean", BuildDate:"2020-07-15T16:10:45Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
 
helm3 version
version.BuildInfo{Version:"v3.2.1", GitCommit:"fe51cd1e31e6a202cba7dead9552a6d418ded79a", GitTreeState:"clean", GoVersion:"go1.13.10"}

Find error:

helm-operator  synchronization of release 'goldpinger' in namespace 'monitoring' failed: failed to prepare chart for release: chart unavailable: chart "goldpinger" version "3.0.0" not found in https://charts.helm.sh/stable repository

How to reproduce it (as minimally and precisely as possible):

helm3 upgrade -i goldpinger  stable/goldpinger  --namespace monitoring --version 3.0.0
Error: failed to download "stable/goldpinger" (hint: running `helm repo update` may help)

helm3 repo list
NAME         	URL
stable       	https://charts.helm.sh/stable

helm3 upgrade -i goldpinger  stable/goldpinger  --namespace monitoring
WARNING: This chart is deprecated
Release "goldpinger" has been upgraded. Happy Helming!
NAME: goldpinger
LAST DEPLOYED: Thu Feb 18 18:10:11 2021
NAMESPACE: monitoring
STATUS: deployed
REVISION: 2
TEST SUITE: None
NOTES:
##################################
# This chart has been deprecated #
##################################
....

helm3 list
NAME      	NAMESPACE 	REVISION	UPDATED                                	STATUS  	CHART                       	APP VERSION
goldpinger	monitoring	2       	2021-02-18 18:10:11.139713319 +0300 MSK	deployed	goldpinger-2.0.4            	2.0.0

Goldpinger-5.3.0 and 5.4.0 is broken

Is this a request for help?: yes

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): bug report

Version of Helm and Kubernetes: any versions

Which chart: goldpinger-5.4.0

What happened:

  Error: Failed to render chart: exit status 1: Error: YAML parse error on goldpinger/templates/daemonset.yaml: error converting YAML to JSON: yaml: line 54: did not find expected key

What you expected to happen: successful chart upgrade

How to reproduce it (as minimally and precisely as possible): write values.yaml with "resources:" section (cpu+mem, requests+limits) and try to install chart with this values file.

Anything else we need to know: seems like there is unneeded spaces in templates/daemonset.yaml just before reference to .Values.resources

Support for loadBalancerSourceRanges in Goldpinger

FEATURE REQUEST:

Please add support for loadBalancerSourceRanges.

Goldpinger Ingress - Should move to apiVersion: networking.k8s.io/v1

Is this a request for help?: Yes, or I can PR it if you'll let me

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature-ish / Avoid Deprecation

Version of Helm and Kubernetes: Helm 3. Kubernetes 1.14 +

Which chart: goldpinger

What happened: The Ingress object is using apiVersion: extensions/v1beta1. extensions/v1beta1 Ingress is deprecated in Kubernetes v1.14+, unavailable in Kubernetes v1.22+; this chart should use networking.k8s.io/v1 Ingress. In my use case it is breaking my integration with aws-load-balancer-controller which relies on networking.k8s.io/v1 Ingress so I can't use the upstream repo..

What you expected to happen: Ingress.yaml should not use a deprecated API. It should use networking.k8s.io/v1 Ingress

How to reproduce it (as minimally and precisely as possible): Deploy the chart

Anything else we need to know: Rules spec will need to change too, likely:

  rules:
  {{- range .Values.ingress.hosts }}
    - host: {{ . }}
      http:
        paths:
          - path: {{ $ingressPath }}
            pathType: Prefix
            backend:
              service:
                name: {{ $fullName }}
                port:
                  name: http
  {{- end }}

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update actions/checkout digest to 692973e
• chore(deps): update helm/kind-action action to v1.10.0

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update python docker tag to v3.12

Detected dependencies

github-actions

.github/workflows/charts_release.yml

• actions/checkout v4@3df4ab11eba7bda6032a0b82a6bb43b11571feac
• azure/setup-helm v4
• helm/chart-releaser-action v1.6.0

.github/workflows/lint_test.yaml

• actions/checkout v4@3df4ab11eba7bda6032a0b82a6bb43b11571feac
• azure/setup-helm v4
• actions/setup-python v5
• helm/chart-testing-action v2.6.1
• helm/kind-action v1.9.0

helm-values

charts/asprom/values.yaml

• okgolove/asprom 1.10.1

charts/aws-xray/values.yaml

charts/goldpinger/values.yaml

charts/kuttle/values.yaml

• python 3.7-alpine

---

• Check this box to trigger a request for Renovate to run again on this repository

AWS X-Ray. Container commend seems to be wrong.

Getting following error when installing x-ray daemon using the latest aws-xray-3.1.0 chart.
Error:

Error: failed to start container "xray-daemon": Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "/usr/bin/xray": stat /usr/bin/xray: no such file or directory: unknown

Looking at chart container command and dockerfile entrypoint it is clear that those don't match.

It seems that there were no changes on filepath (dockerfile) nor command (chart). So I'm wondering how the chart supposed to work for anyone.

Can be fixed in couple ways:
Maybe we can make command configurable with current value as default in values.yaml(in case it works for someone with older image tags, so we can keep backward compatibility).
Or just update the command with valid executable path.

Happy to provide a PR on that.