ArgoCD init hangs

[Homulvas]

I'm attempting to run the v0.45 helm chart. I've configured the following env values:

    KUBECHECKS_VCS_TYPE: "github",
    KUBECHECKS_LOG_LEVEL: "trace",
    KUBECHECKS_MONITOR_ALL_APPLICATIONS: "true",
    KUBECHECKS_ARGOCD_API_INSECURE: "true",
    KUBECHECKS_ARGOCD_API_TOKEN: <token>,

The application appears to start and then hangs just before ArgoCD client should be created. The application eventually gets restarted as healthchecks never pass. There is no error or any indication whatsoever as to what could be wrong.

Logs:

7:36AM DBG Debug level logging enabled.
7:36AM TRC Trace level logging enabled.
7:36AM INF Initialized logger.
7:36AM INF setting logrus log level log_level=error
7:36AM INF Starting KubeChecks git-commit=ebf376b git-tag=v1.7.0
7:36AM INF parsing configuration
7:36AM INF Server Configuration:
7:36AM INF Webhook URL Base:
7:36AM INF Webhook URL Prefix:
7:36AM INF VCS Type: github
7:36AM INF ArgoCD Namespace: argocd
7:36AM DBG Token Length - 40
7:36AM INF ArgoCD client configuration auth-token=243 grpc-web-root-path= insecure=true server-addr=argocd-server

[Greyeye]

kubechecks will use default hostname argocd-server if it's not specified try setting values for these two env var.

KUBECHECKS_ARGOCD_API_INSECURE : false KUBECHECKS_ARGOCD_API_SERVER_ADDR : argocd-hostname.company.com

[Homulvas]

kubechecks will use default hostname argocd-server if it's not specified try setting values for these two env var.

KUBECHECKS_ARGOCD_API_INSECURE : false KUBECHECKS_ARGOCD_API_SERVER_ADDR : argocd-hostname.company.com

argocd-server is running on the same namespace so the default value should be correct. I've also tried argocd-server.argocd.svc.cluster.local with the same result.

[Homulvas]

Ok so after some further investigation it appears that I was missing some Istio configuration and I am now blocked on #168

[djeebus]

Just released v1.8.0, which includes the fix for #168 , give it a try?