Skip to content
English
  • There are no suggestions because the search field is empty.

"Logs Not Found" from Completed Verification Tasks

Unable to view logs from completed Kargo Verification Tasks

Error Message

When attempting to view logs from completed verification tasks, you may see errors like:

From UI:
{"error":{"code":5,"message":"logs not found"}}

From controller/syncer:
"msg":"Failed to stream logs, max attempts reached","namespace":"akuity","job":"8eff2058-968e-472b-bd33-f310ec021b8d.snyk-scan.1","error":"failed to stream logs for container snyk, failed to send request: Post \"https://<instance-id>.kargo.akuity.cloud/agent-api/v1/stream/kargo/agent/logs\": dial tcp: lookup <instance-id>.kargo.akuity.cloud on 172.20.0.10:53: no such host"

Root Cause

The managed cluster where the self-hosted Kargo agent is deployed does not have DNS resolution or network access to <instance-id>.kargo.akuity.cloud. The agent inherits DNS and network configuration from its managed cluster and needs to stream verification task logs to the /agent-api/v1/stream endpoint on the control plane.

Solution

1. Verify Network Connectivity

Test connectivity from a pod in the managed cluster:

# Test DNS resolution
kubectl run -it --rm debug --image=nicolaka/netshoot:latest --restart=Never -- \
nslookup <instance-id>.kargo.akuity.cloud

# Test TCP connectivity to port 443
kubectl run -it --rm debug --image=nicolaka/netshoot:latest --restart=Never -- \
nc -zv <instance-id>.kargo.akuity.cloud 443

Replace <instance-id> with your Kargo instance ID. If you have configured a custom Akuity Subdomain or Fully Qualified Domain Name in Kargo → Settings → External Access, use that hostname instead.

2. Configure DNS and Network Access

If connectivity tests fail, ensure the managed cluster has DNS resolution and network connectivity to the Akuity Platform control plane.
Key requirements include allowing egress traffic on port 443 (TCP) and permitting access to *.kargo.akuity.cloud domains.