-
Notifications
You must be signed in to change notification settings - Fork 550
Description
📜 Description
Created a kind cluster on 1.22.7 k8s version.
Installed devtron using helm chart.
When tried to install GitOps (Argo CD) from the UI, it got stuck in installing state and I see argocd-application-controller and argocd-server pods are in CrashLoopBackOff state.
argocd-application-controller-0 pod logs
argocd-server pod logs:
👟 Reproduction steps
Install a kind cluster with below kind configurations:
`kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
networking:
podSubnet: "10.214.0.0/16"
serviceSubnet: "10.16.0.0/12"
nodes:
- role: control-plane
image: kindest/node:v1.22.7@sha256:1dfd72d193bf7da64765fd2f2898f78663b9ba366c2aa74be1fd7498a1873166
extraPortMappings:- containerPort: 30000
hostPort: 30000
- containerPort: 30000
- role: worker
image: kindest/node:v1.22.7@sha256:1dfd72d193bf7da64765fd2f2898f78663b9ba366c2aa74be1fd7498a1873166 - role: worker
image: kindest/node:v1.22.7@sha256:1dfd72d193bf7da64765fd2f2898f78663b9ba366c2aa74be1fd7498a1873166 `
and use devtron helm chart to install devtron
👍 Expected behavior
When installing Argo CD. Pods should spin up and installation should be successful.
👎 Actual Behavior
Argo pods go into CrashLoopBackOff state
💻 Device
Desktop/Laptop
💻 Operating system
MacOS
🌍 Browser
Chrome
🧱 Your Environment
I use kind for creating a k8s version 1.22.7 cluster
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
- I checked and didn't find any similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
AB#620