Live Resources

A core aspect of ConfigHub is that it maintains a one-to-one correspondence between configuration and corresponding live resources. The word "Live" is used to distinguish the configuration from the actual resources instantiated in the system under management.

For example, a Config Unit may represent a Kubernetes workload, such as a Deployment, Service, Ingress, and related resources. At any given time, this Unit may be "live" or "not live". Being live means that resources specified in the Unit have been created and exist in some Kubernetes cluster. If the Unit is in the state of "No Live", it means that the resources specified by the Unit have either never existed or have been destroyed and do not exist any longer.

See Unit Actuation Lifecycle for more details.