Stable releases?

[henrik-farre]

Describe the enhancement you'd like to see
Current I'm trying to upgrade to a newer version of the helm chart, but I keep running into issues. Some of the versions can't install because of CRD issues, other times it is the testkube application that givens an error.

When I look at the releases for the helm chart I do not see any release notes that indicate I have to change anything or do something special to upgrade.

Currently I'm at helm chart 1.7.15 and have tried versions up until 1.7.48 (also clean installs).

Are all these versions development or pre-releases?

I would very much like to see stable releases with changelogs ❤️

[devantler]

I am in the same boat as Henrik.

This is our latest working release:

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: testkube
spec:
  interval: 5m
  install:
    crds: CreateReplace
  upgrade:
    crds: CreateReplace
  chart:
    spec:
      chart: testkube
      version: 1.17.20
      sourceRef:
        kind: HelmRepository
        name: testkube
  # https://github.com/kubeshop/helm-charts/blob/develop/charts/testkube/values.yaml
  values:
    global:
      imageRegistry: ${testkube_image_registry:=docker.io}

[vsukhin]

hey, guys! Sorry, we had a testkube application bug in a few latest releases we didn't note, around 1.17.25, it was fixed in 1.17.33

regarding CRD issues, do I understand right, that this is related to test workflow template resource creation? It should be done in Helm post hook @tkonieczny

[henrik-farre]

Let me just spin up a cluster and give you the precise error, ~30min.

[vsukhin]

thank you!

[henrik-farre]

> helm pull kubeshop/testkube --version 1.17.48
> # unpack chart
> helm install testkube .
coalesce.go:286: warning: cannot overwrite table with non table for testkube.testkube-api.minio.extraEnvVars (map[])
coalesce.go:286: warning: cannot overwrite table with non table for testkube.testkube-api.minio.extraEnvVars (map[])
coalesce.go:286: warning: cannot overwrite table with non table for testkube.testkube-api.minio.extraEnvVars (map[])
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: resource mapping not found for name: "distribute--evenly" namespace: "" from "": no matches for kind "TestWorkflowTemplate" in version "testworkflows.testkube.io/v1"
ensure CRDs are installed first
zsh: exit 1     helm install testkube .

This is on a clean minikube cluster

Same result on a cloud provided cluster

[vsukhin]

I see, this is what I thought about. Let us check it outt

[vsukhin]

temp workround is to exclude this folder from installation https://github.com/kubeshop/helm-charts/tree/develop/charts/testkube-api/templates/testworkflows/builtin-templates

[vsukhin]

@henrik-farre released a fix for help. can you try it now?

[henrik-farre]

Give me ~10min

[henrik-farre]

> helm install testkube .
coalesce.go:286: warning: cannot overwrite table with non table for testkube.testkube-api.minio.extraEnvVars (map[])
coalesce.go:286: warning: cannot overwrite table with non table for testkube.testkube-api.minio.extraEnvVars (map[])
coalesce.go:286: warning: cannot overwrite table with non table for testkube.testkube-api.minio.extraEnvVars (map[])
W0517 14:24:48.050983   48925 warnings.go:70] spec.template.spec.containers[1].ports[0]: duplicate port definition with spec.template.spec.containers[0].ports[0]
NAME: testkube
LAST DEPLOYED: Fri May 17 14:24:23 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Enjoy testing with Testkube!

Works better in minikube, testing in cloud

[henrik-farre]

We are still investigating problems in cloud cluster, I will update this issue next week when I had time to debug

[vsukhin]

sure, ping us when you have more info. thank you!

[vsukhin]

should be fixed

[henrik-farre]

We also use GitOps (not ArgoCD) and it looks like our problem is CRDs not being created. It also looks like other people have reported this #711 kubeshop/testkube#5280 #627

Keep this closed, I will create a new issue if needed.

[vsukhin]

yes, please, open a separated issue with errors from ArgoCD @henrik-farre