Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helm Upgrade fails on 'deployment' template #1313

Open
2 tasks done
moriisaac-gramx opened this issue Jan 17, 2025 · 8 comments
Open
2 tasks done

Helm Upgrade fails on 'deployment' template #1313

moriisaac-gramx opened this issue Jan 17, 2025 · 8 comments
Labels
kind/bug/possible a possible bug that needs analysis before it is confirmed or fixed.

Comments

@moriisaac-gramx
Copy link

Welcome!

  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?

34.1.0

What version of Traefik are you using?

3.3.2

What did you do?

I was running a helm upgrade on the chart using custom values.yaml with the following command. helm upgrade --install traefik traefik/traefik -f values-dev.yaml --dry-run --debug --namespace=gateway-system

and this is after the new reelease was done

What did you see instead?

Error: UPGRADE FAILED: YAML parse error on traefik/templates/deployment.yaml: error converting YAML to JSON: yaml: line 109: did not find expected '-' indicator
helm.go:86: 2025-01-17 23:33:18.4785364 +0300 EAT m=+94.393238301 [debug] error converting YAML to JSON: yaml: line 109: did not find expected '-' indicator
YAML parse error on traefik/templates/deployment.yaml
helm.sh/helm/v3/pkg/releaseutil.(*manifestFile).sort
helm.sh/helm/v3/pkg/releaseutil/manifest_sorter.go:144
helm.sh/helm/v3/pkg/releaseutil.SortManifests
helm.sh/helm/v3/pkg/releaseutil/manifest_sorter.go:104
helm.sh/helm/v3/pkg/action.(*Configuration).renderResources
helm.sh/helm/v3/pkg/action/action.go:168
helm.sh/helm/v3/pkg/action.(*Upgrade).prepareUpgrade
helm.sh/helm/v3/pkg/action/upgrade.go:276
helm.sh/helm/v3/pkg/action.(*Upgrade).RunWithContext
helm.sh/helm/v3/pkg/action/upgrade.go:165
main.newUpgradeCmd.func2
helm.sh/helm/v3/cmd/helm/upgrade.go:240
github.com/spf13/cobra.(*Command).execute
github.com/spf13/[email protected]/command.go:985
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/[email protected]/command.go:1117
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/[email protected]/command.go:1041
main.main
helm.sh/helm/v3/cmd/helm/helm.go:85
runtime.main
runtime/proc.go:271
runtime.goexit
runtime/asm_amd64.s:1695
UPGRADE FAILED
main.newUpgradeCmd.func2
helm.sh/helm/v3/cmd/helm/upgrade.go:243
github.com/spf13/cobra.(*Command).execute
github.com/spf13/[email protected]/command.go:985
github.com/spf13/cobra.(*Command).ExecuteC
github.com/spf13/[email protected]/command.go:1117
github.com/spf13/cobra.(*Command).Execute
github.com/spf13/[email protected]/command.go:1041
main.main
helm.sh/helm/v3/cmd/helm/helm.go:85
runtime.main
runtime/proc.go:271
runtime.goexit
runtime/asm_amd64.s:1695

What is your environment & configuration?

I'm running on k8s and my implementation is of the k8s gateway api with traefik

Additional Information

@PahaCore
Copy link

I also decided to update and everything stopped working, I had to roll back, I have k3s, but I put the traffic separately through helm

@moriisaac-gramx
Copy link
Author

I also decided to update and everything stopped working, I had to roll back, I have k3s, but I put the traffic separately through helm

It seems it's something about the update done? I will have to roll back to the previous chart version

@darkweaver87
Copy link
Contributor

Hello @moriisaac-gramx and @PahaCore,

Thanks for reporting this.
While I'm trying to reproduce, could you provide the helm chart version you were upgrading from ?
Also, could you provide your values (obfuscated if needed) ?

Thanks,

Rémi

@mloiseleur mloiseleur added kind/bug/possible a possible bug that needs analysis before it is confirmed or fixed. and removed status/0-needs-triage labels Jan 20, 2025
@PahaCore
Copy link

PahaCore commented Jan 20, 2025

Hell @darkweaver87

28 Fri Jan 10 19:28:14 2025 superseded traefik-33.2.1 v3.2.2 Upgrade complete
29 Sat Jan 18 18:47:44 2025 superseded traefik-34.1.0 v3.3.2 Upgrade complete
30 Sat Jan 18 20:37:35 2025 deployed traefik-33.2.1 v3.2.2 Rollback to 28

@darkweaver87
Copy link
Contributor

Hello @moriisaac-gramx and @PahaCore,

Could you provide your values ?
I haven't been able to reproduce on my side with some minimal values I used to use.

Rémi

@PahaCore
Copy link

PahaCore commented Jan 30, 2025

@darkweaver87 I don't want to specify it, but I've updated it to the new helm traefik-34.2.0 v3.3.2 - and there is no problem anymore, everything is working well
Providers: File, KubernetesIngress, KubernetesCRD

@darkweaver87
Copy link
Contributor

@moriisaac-gramx is it fixed on your side as well ?
If it's case, as I'm not able to reproduce and @PahaCore can't provide a values.yaml, I will close this issue.

@moriisaac-gramx
Copy link
Author

moriisaac-gramx commented Jan 31, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug/possible a possible bug that needs analysis before it is confirmed or fixed.
Projects
None yet
Development

No branches or pull requests

4 participants