Skip to main content
Version: v3.9.0

Operate

Operate guides cover day-2 tasks after cluster resources exist: deploy updates, inspect status, move nodes, stream logs, open exec sessions, and roll the platform train forward.

Each Configure page includes a short Operate this resource section with Console paths and common CLI verbs. Use this hub when you need end-to-end walkthroughs.

Prerequisites​

Before you operate an ECN:

  1. Install potctl matching your platform train (see the potctl download page).
  2. Connect to the control plane or deploy a new one. See Control plane.
  3. Sign in to EdgeOps Console with the same OIDC identity as the CLI. Open it with potctl view or your controller.consoleUrl.

Namespaces scope every command. Use -n or potctl configure current-namespace when you work outside default.

Console and CLI together​

ToolBest for
EdgeOps ConsoleFleet visibility, YAML edits with validation, exec and logs in the browser, audit events
potctlFirst control plane install, Edgelet provisioning over SSH, automation, CI pipelines

Console menu labels match the Configure sidebar: Platform, Nodes, Workloads, Config, Network, Message bus, and Access control. The dashboard summarizes ECN health before you drill into a section.

Initial control plane deploy and Edgelet node install are CLI-only. After resources exist, Console and CLI share the same Controller REST API and RBAC rules.

Operate guides​

Guides follow the same order as Configure:

AreaGuideConfigure reference
Control planeControl planeControl plane
Edgelet nodesLifecycleEdgelet nodes
WorkloadsWorkloadsApplications, Microservices
ConfigurationConfigurationRegistries, secrets, catalogs, and related objects
Network and messagingNetwork, Message busServices, Account rules, User rules
Access controlAccess controlRoles, bindings, and service accounts. Bus subjects are on Message bus.
Observe and troubleshootObserve and troubleshootEdgelet troubleshooting, Controller logs
Node logs and execNode logs and execlogs agent and exec agent

For production install paths before day-2 work, start at Platform deployment or Quick start (local).

Typical workflows​

Stand up a new ECN​

  1. Author control plane YAML (Configure control plane).
  2. potctl deploy -f controlplane.yaml.
  3. potctl view and sign in to Console.
  4. Deploy fleet Edgelet nodes with kind: Agent YAML (Edgelet nodes).

Join an existing ECN​

  1. potctl connect with a minimal control plane manifest or flags.
  2. Confirm with potctl describe controlplane.
  3. Use Console or CLI for workloads and config.

Move the platform train (v3.8 → v3.9)​

Stay on one train across Controller, Operator, Router, NATS, potctl, and Edgelet. High-level steps live in Upgrade the platform train and Upgrade and rollback Edgelet. Release notes and breaking YAML changes are in What's New.