Skip to content

VM pods: switch engine/cocoon from SSH + CLI to a cocoon daemon API when one exists #662

Description

@CMGS

Sub-issue of #657. engine/cocoon drives cocoon over SSH by executing the CLI on the node; the read-only daemon socket (/v1/vms, /v1/events) is used by eru-agent locally only. If the cocoon daemon grows a remote gRPC/mTLS control API, the engine swaps transports without changing the verb mapping.

Optional; SSH + CLI is the agreed baseline and is not blocked.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions