Self-test
kaironctl selftest answers the question every install ends with. It runs the
User guide: metrics and alerts
Until now, Kairon's Prometheus metrics were kairon-controller-only and
User guide: running more than one kairon-controller replica
controller.replicaCount (Helm chart, default 1) can be raised for HA --
User guide: MachineQuota
Caps how many Machines, and how much total CPU/memory, a namespace may have
User guide: MachineDisruptionBudget
Caps how many Machines kaironctl evacuate is willing to disrupt at once.
Guarding the fleet (admission webhook)
Also see machine-quotas.md and machine-disruption-budgets.md.
User guide: CRD versioning and the conversion webhook scaffold
Every kairon.zyvor.dev CRD serves three versions with an identical schema:
Enterprise fleet automation (experimental)
This opt-in extension uses fleet.kairon.zyvor.dev/v1alpha1 resources and existing Kairon Machine, migration, backup, restore, pool and set primitives. It does not introduce a second hypervisor. Review the status below before deploying; this is a draft feature set needing cluster and hardware validation.
Enterprise fleet reference
Per-kind reference for the fleet.kairon.zyvor.dev/v1alpha1 custom resources. For the feature status matrix, installation prerequisites and caveats read Enterprise fleet automation first. Everything here is experimental and opt-in: nothing below runs unless fleet.enabled (Helm) / --fleet-enabled (controller) is set, and the feature set still needs cluster and hardware validation.