Appendix A. KataConfig status messages The following table displays the status messages for the KataConfig custom resource (CR) for a cluster with two worker nodes. Table A.1. KataConfig status messages Status Description Initial installation When a KataConfig CR is created and starts installing kata-remote on both workers, the following status is displayed for a few seconds. conditions: message: Performing initial installation of kata-remote on cluster reason: Installing status: 'True' type: InProgress kataNodes: nodeCount: 0 readyNodeCount: 0 Installing Within a few seconds the status changes. kataNodes: nodeCount: 2 readyNodeCount: 0 waitingToInstall: - worker-0 - worker-1 Installing (Worker-1 installation starting) For a short period of time, the status changes, signifying that one node has initiated the installation of kata-remote , while the other is in a waiting state. This is because only one node can be unavailable at any given time. The nodeCount remains at 2 because both nodes will eventually receive kata-remote , but the readyNodeCount is currently 0 as neither of them has reached that state yet. kataNodes: installing: - worker-1 nodeCount: 2 readyNodeCount: 0 waitingToInstall: - worker-0 Installing (Worker-1 installed, worker-0 installation started) After some time, worker-1 will complete its installation, causing a change in the status. The readyNodeCount is updated to 1, indicating that worker-1 is now prepared to execute kata-remote workloads. You cannot schedule or run kata-remote workloads until the runtime class is created at the end of the installation process. kataNodes: installed: - worker-1 installing: - worker-0 nodeCount: 2 readyNodeCount: 1 Installed When installed, both workers are listed as installed, and the InProgress condition transitions to False without specifying a reason, indicating the successful installation of kata-remote on the cluster. conditions: message: "" reason: "" status: 'False' type: InProgress kataNodes: installed: - worker-0 - worker-1 nodeCount: 2 readyNodeCount: 2 Status Description Initial uninstall If kata-remote is installed on both workers, and you delete the KataConfig to remove kata-remote from the cluster, both workers briefly enter a waiting state for a few seconds. conditions: message: Removing kata-remote from cluster reason: Uninstalling status: 'True' type: InProgress kataNodes: nodeCount: 0 readyNodeCount: 0 waitingToUninstall: - worker-0 - worker-1 Uninstalling After a few seconds, one of the workers starts uninstalling. kataNodes: nodeCount: 0 readyNodeCount: 0 uninstalling: - worker-1 waitingToUninstall: - worker-0 Uninstalling Worker-1 finishes and worker-0 starts uninstalling. kataNodes: nodeCount: 0 readyNodeCount: 0 uninstalling: - worker-0 Note The reason field can also report the following causes: Failed : This is reported if the node cannot finish its transition. The status reports True and the message is Node <node_name> Degraded: <error_message_from_the_node> . BlockedByExistingKataPods : This is reported if there are pods running on a cluster that use the kata-remote runtime while kata-remote is being uninstalled. The status field is False and the message is Existing pods using "kata-remote" RuntimeClass found. Please delete the pods manually for KataConfig deletion to proceed . There could also be a technical error message reported like Failed to list kata pods: <error_message> if communication with the cluster control plane fails.

Commands:
conditions: message: Performing initial installation of kata-remote on cluster reason: Installing status: 'True' type: InProgress kataNodes: nodeCount: 0 readyNodeCount: 0
kataNodes: nodeCount: 2 readyNodeCount: 0 waitingToInstall: - worker-0 - worker-1
kataNodes: installing: - worker-1 nodeCount: 2 readyNodeCount: 0 waitingToInstall: - worker-0
kataNodes: installed: - worker-1 installing: - worker-0 nodeCount: 2 readyNodeCount: 1
conditions: message: "" reason: "" status: 'False' type: InProgress kataNodes: installed: - worker-0 - worker-1 nodeCount: 2 readyNodeCount: 2
conditions: message: Removing kata-remote from cluster reason: Uninstalling status: 'True' type: InProgress kataNodes: nodeCount: 0 readyNodeCount: 0 waitingToUninstall: - worker-0 - worker-1
kataNodes: nodeCount: 0 readyNodeCount: 0 uninstalling: - worker-1 waitingToUninstall: - worker-0
kataNodes: nodeCount: 0 readyNodeCount: 0 uninstalling: - worker-0