Cell and Composites can be managed by,
Cellery Observability brings along the capability to observe the Cells deployed on Cellery Mesh. It provides overview of the deployed cells with dependency diagrams, runtime metrics of the cells, and distributed tracing for the request that pass through each cells and components. By default cellery obserability component is enabled only in the complete setup. You can also enable the observability component via the modify commands. Find more details on how to observe cells here.
Each components within the cells can optionally have auto scaling or zero scaling policies as explained here. Therefore, a component within a cell can be scaled up to maximum replica count, and scaled down upto minimum replica count based on the metrics threshold defined in the policy. Auto scaling is handled by kubernetes horizontal autoscaler, and zero scaling is powered by Knative. By default cellery installations have autoscaling, and zero scaling disabled in the runtime, and you can enable it by modify commands. Find more details on scaling up/down cells here.
Cell/Composite instances are only allowed to be updated restrictively. Its possible to patch components of cell/composite instances, and this is a viable operation when there are no breaking changes to the components. Further, as advanced deployment methods, Cellery supports both blue-green and canary deployment options. In that case, a new instance with updated version will be spawned along with the old cell instance, and the traffic can be routed to completely or partially to the new instance. Find more details on updating cell components and advanced deployment patterns here.
Cell APIs can be optionally versioned, and exposed from the cell gateway or global gateway. Refer api versioning documentation for further details.