Microservice Updates and Lifecycle

Microservice Updates

We can modify Microservices through the same Microservice kind that we deploy them with.

To help us with this, a Microservice YAML spec of a deployed Microservice can be retrieved using the describe command:

potctl describe microservice msvc-1 -o /tmp/msvc.yaml

With the msvc.yaml file generated for us, we can make changes to the spec and run deploy again to make modifications to the existing Microservice.

potctl deploy -f /tmp/msvc.yaml

Microservice States

Once we deploy a Microservice, the Agent that hosts it will report the Microservice's status back to the Controller.

The Microservice could be in one of various states including starting, pulling, running, or deleting.

We can view this status by running:

potctl get microservices

NAMESPACE
default

MICROSERVICE  STATUS    AGENT     ROUTES    VOLUMES           PORTS
msvc-1        RUNNING   agent-1   route-1   /tmp/msvc:/tmp
msvc-2        DELETING  agent-2             /tmp/iofog:/data  5000:8

When we manage a deployed Microservice through commands like move, deploy, and delete, we can expect the Microservice to transition between states.

See anything wrong with the document? Help us improve it!