Closed AydinChavez closed 1 year ago
fixed the redis issue by setting bind 0.0.0.0 but the 404 when opening the browser in order to access the UI remains
the configmap argocd-cmd-params-cm looks also valid ?
apiVersion: v1
data:
controller.log.format: text
controller.log.level: info
controller.operation.processors: "10"
controller.repo.server.timeout.seconds: "60"
controller.self.heal.timeout.seconds: "5"
controller.status.processors: "20"
otlp.address: ""
redis.server: argocd-redis-ha-haproxy:6379
repo.server: argocd-repo-server:8081
reposerver.log.format: text
reposerver.log.level: info
reposerver.parallelism.limit: "0"
server.basehref: /
server.disable.auth: "false"
server.enable.gzip: "false"
server.insecure: "true"
server.log.format: text
server.log.level: debug
server.rootpath: /
server.staticassets: /shared/app
server.x.frame.options: sameorigin
timeout.hard.reconciliation: "0"
timeout.reconciliation: "180"
kind: ConfigMap
metadata:
annotations:
meta.helm.sh/release-name: argocd
meta.helm.sh/release-namespace: argocd
creationTimestamp: "2022-09-21T14:44:49Z"
labels:
app.kubernetes.io/component: server
app.kubernetes.io/instance: argocd
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: argocd-cmd-params-cm
app.kubernetes.io/part-of: argocd
helm.sh/chart: argo-cd-5.5.0
name: argocd-cmd-params-cm
namespace: argocd
resourceVersion: "53568254"
uid: 260b815e-e6ee-41bc-a5ac-81058188b63b
Could it depend on "insecure: true" setting?
It is set. Tried setting it with extraParams before also
Get same error since updated argo from 4.4.0 to 5.5.0
Restarting pods also not helped
Downgrade argo via helm to 4.4.8 fixed this issue
Downgrade argo via helm to 4.4.8 fixed this issue
Thanks a lot. I will also give it a try.
Same issue here. DOes it worth opening an issue in https://github.com/argoproj/argo-helm/issues
Same issue here. DOes it worth opening an issue in https://github.com/argoproj/argo-helm/issues
Its a bug with 5.5.0 latest 4.4 version works (4.4.8)
Its a bug with 5.5.0 latest 4.4 version works (4.4.8)
mind you share your values.yml? I still get same issue with 4.4.8. Which helm image tag is chart v4.4.8 using, do you know?
I use rancher :D i just set select version an then select 4.4.8 and it works again.
sorry very long
Workaround is described here guys: https://github.com/argoproj/argo-helm/issues/1479#issuecomment-1254089715
I think I basicly waiting for 5.5.1 :D and go with 4.4.8 instead of dirty hacks
Checklist:
argocd version
.Describe the bug
When executing
kubectl port-forward svc/argocd-server -n argocd 9999:443
I get a 404 in the browser (localhost:9999)
To Reproduce
Chart.yaml
values.yaml
installation via helm: helm install argocd . -n argocd
Expected behavior
No 404
Screenshots
Version
Logs
argocd-server log: