ARGOCD_SERVER doesn't honor fqdn about argocd-image-updater HOT 10 CLOSED

@matoszz sir I had enabled ingressGrpc to true value bur still getting the error. Could you please let me know how to resolve it?
ERROR:: application.ApplicationService/Create failed with status code 502

from argocd-image-updater.

Trying all permutations of options (INSECURE true vs. false, GRPC_WEB true vs. false) still yields unsuccessful connection attempts even when hitting the pod IP's directly:

time="2020-10-08T21:53:01Z" level=error msg="error while communicating with ArgoCD" argocd_server=argocd-server.argocd grpc_web=false gr
pc_webroot= insecure=false plaintext=false
time="2020-10-08T21:53:01Z" level=error msg="Error: read tcp 192.168.3.122:55310->192.168.1.64:8080: read: connection reset by peer"

from argocd-image-updater.

Hi, please try if a non-URL value for ARGOCD_SERVER, i.e. argo.mydomain.com or argo.mydomain.com:443 (without the protocol specified) works for you.

from argocd-image-updater.

ARGOCD_SERVER = argo.mydomain.com + ARGOCD_GRPC_WEB = false + ARGOCD_INSECURE = true

time="2020-10-12T01:44:03Z" level=error msg="Error: rpc error: code = Internal desc = transport: received the unexpected content-type \"
text/plain; charset=utf-8\""

ARGOCD_SERVER = argo.mydomain.com + ARGOCD_GRPC_WEB = true + ARGOCD_INSECURE = true

time="2020-10-12T01:55:11Z" level=error msg="Error: rpc error: code = Unauthenticated desc = no session information"

ARGOCD_SERVER = argo.mydomain.com + ARGOCD_GRPC_WEB = false + ARGOCD_INSECURE = false

time="2020-10-12T01:57:00Z" level=error msg="Error: rpc error: code = Internal desc = transport: received the unexpected content-type \"
text/plain; charset=utf-8\""

ARGOCD_SERVER = argo.mydomain.com + ARGOCD_GRPC_WEB = true + ARGOCD_INSECURE = false

time="2020-10-12T02:01:29Z" level=error msg="Error: rpc error: code = Unauthenticated desc = no session information"

ARGOCD_SERVER = argo.mydomain.com:443 + ARGOCD_GRPC_WEB = false + ARGOCD_INSECURE = true

time="2020-10-12T01:46:13Z" level=error msg="Error: rpc error: code = Internal desc = transport: received the unexpected content-type \"
text/plain; charset=utf-8\""

ARGOCD_SERVER = argo.mydomain.com:443 + ARGOCD_GRPC_WEB = true + ARGOCD_INSECURE = false

time="2020-10-12T01:48:39Z" level=error msg="Error: rpc error: code = Unauthenticated desc = no session information"

ARGOCD_SERVER = argo.mydomain.com:443 + ARGOCD_GRPC_WEB = false + ARGOCD_INSECURE = false

time="2020-10-12T01:50:05Z" level=error msg="Error: rpc error: code = Internal desc = transport: received the unexpected content-type \"
text/plain; charset=utf-8\""

ARGOCD_SERVER = argo.mydomain.com:443 + ARGOCD_GRPC_WEB = true + ARGOCD_INSECURE = true

time="2020-10-12T01:53:05Z" level=error msg="Error: rpc error: code = Unauthenticated desc = no session information"

from argocd-image-updater.

trying to rule out the ingress; disabling default backend, creating a dedicated gRPC ingress, results in:

/application.ApplicationService/List failed with status code 502

from argocd-image-updater.

If you receive a message such as Error: rpc error: code = Unauthenticated desc = no session information, it means that the connection parameters actually were correct, but that authentication is required at the endpoint. Credentials can be supplied via ARGOCD_TOKEN environment variable.

I agree that the error messages could be a little bit more helpful on connection issues with the Argo CD server, tho.

from argocd-image-updater.

Interesting. I've created the secret per the instructions in the docs but now the secret is empty. I'm noticing that after I create it, restart the pods, it gets wiped out. Any inkling about why that would be occurring?

from argocd-image-updater.

Also, even when I generate the JWT token and put it into the env var of the deployment directly (instead of creating a secret with it) it still fails in the same way. Is there a step I'm missing w/r/t creating the user + JWT token?

from argocd-image-updater.

I finally found the permutation of settings that function 👏 - using not the grpc ingress (the regular one) with GRPC_WEB as "true" and insecure as "false" seems to finally start logging out checks

from argocd-image-updater.

Closing this as I believe has been resolved.

Feel free to reopen if it is not.

from argocd-image-updater.