-
Notifications
You must be signed in to change notification settings - Fork 48
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
Upgrading from 2023.10.7 to 2024.2.3 with argocd, failed with redis template #271
Comments
Just tested a new version with a cluster at v1.27.16+rke2r1, the same error. but I think I found the problem
A look at the file in question and we can see a few empty line after spec and helm dosen't see to like it:
After a few tweek and not using the global imagePullSecrets it work:
The problem is with the global imagePullSecrets, but I can't figured out were the error is in the templating. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Upgrading from 2023.10.7 to 2024.2.3 with argocd, failed with redis template.
Relevant info
Kube version:
v1.26.13+rke2r1
ArgoCD:
v2.10.12+cb6f5ac
Authentik Helm Chart Version:
2024.2.3
Deployment: [helm]
Logs
Failed to load target state: failed to generate manifest for source 1 of 1: rpc error: code = Unknown desc = helm template . --name-template authentik-rke-dev --namespace authentik-rke-dev --kube-version 1.26 --values /tmp/23a262ae-25f2-47e6-92dc-b9f146fb464e --include-crds failed exit status 1: Error: YAML parse error on authentik/charts/redis/templates/master/application.yaml: error converting YAML to JSON: yaml: line 40: mapping values are not allowed in this context Use --debug flag to render out invalid YAML
To Reproduce
Upgrading from
2023.10.7
with this argocd application:To
2024.2.3
This gave me the following error in argocd and prevent further upgrade:
It's seem to pushing this template, but i didn't find any useful information
Removing redis unblock the upgrade, but the server is looking for redis in loop and failed to start
The text was updated successfully, but these errors were encountered: