Event > List of events > Lifecycle events >
This document describes the
“Start” is the point where a Unit agent starts to join its relations and can respond to commands like
start event is triggered on each starting unit immediately after the first
config-changed event. Callback methods bound to the event should be used to ensure that the charm’s software is in a running state. Note that the charm’s software should be configured to persist in a started state without further intervention from Juju or an administrator.
Also, on kubernetes charms, whenever a unit’s pod churns,
start will be fired again on that unit.
|Scenario||Example Command||Resulting Events|
|(k8s only) pod churn||
In kubernetes sidecar charms, Juju provides no ordering guarantees regarding
Observing this event in Ops
ops, you can observe this event like you would any other:
# in MyCharm.__init__ self.framework.observe(self.on.start, self._on_start)
start event object does not expose any specific attributes.
Last updated 5 months ago.