I am encountering a persistent communication issue where drasi apply -f <resource.yaml> fails with a 404 Not Found error. This occurs despite the Drasi control plane pods (drasi-api and drasi-resource-provider) being fully running and healthy.

The error message Source/: 404 Not Found suggests the CLI might be constructing a malformed API request path or there is a routing mismatch in this version.

Reproduction Steps

1. Initialize Drasi v0.10.1 (via drasi init --docker or standard GKE install).
2. Verify all control plane pods are running (e.g., drasi-api is 2/2 Running).
3. Attempt to apply a valid resource configuration (e.g., a File Source):

drasi apply -f source.yaml

4. Result: The command fails immediately.

Observed behavior

The CLI returns the following error, indicating the endpoint cannot be found:

Error: Apply: Source/: 404 Not Found

Debugging & Diagnosis Attempts

1. GKE Sidecar Resolution: On GKE, we initially resolved Dapr sidecar initTimeout and DNS issues. Even after pods stabilized to Running, the 404 persisted.
2. Local Isolation: To rule out GKE ingress/DNS issues, I switched to a clean local setup on macOS (drasi init --docker). The exact same 404 error occurred.
3. In-Cluster Execution: Attempted to use kubectl exec to run commands from within the drasi-api pod, but was blocked by the "distroless" container image limitations (no shell).
4. Connectivity Check: Confirmed kubectl port-forward is active. The "404" response implies the server is reachable but is rejecting the specific route requested by the CLI.

Desired behavior

Drasi functions normally

Workaround

No response

Drasi Version

• Drasi CLI/Platform Version: v0.10.1

Operating system

I have reproduced this behavior in two distinct environments, ruling out specific cloud network restrictions:

Environment 1: Local Development

• OS: macOS Sequoia (MacBook Air)
• Drasi Deployment: Local Docker (drasi init --docker)
• Kubernetes Backend: k3s (embedded in the Drasi Docker container)

Environment 2: Cloud Cluster

• Platform: Google Kubernetes Engine (GKE)
• Connectivity: Accessed via kubectl port-forward to the API service.

Additional context

No response

Would you like to support us?

• Yes, I would like to support you