update runtimeClass, binary naming

Signed-off-by: Eric Ernst <eric.ernst@intel.com>

clr-k8s-examples/8-kata/kata-fc-runtimeClass.yaml

@@ -1,6 +1,6 @@
 kind: RuntimeClass
 apiVersion: node.k8s.io/v1alpha1
 metadata:
-    name: fire
+    name: kata-fc
 spec:
-    runtimeHandler: fire
+    runtimeHandler: kata-fc

clr-k8s-examples/README.md

@@ -24,7 +24,7 @@ This script ensures the following
 
 ### Enabling experimental firecracker support
 
-> EXPERIMENTAL: Optionally run [`setup_firecracker.sh`](setup_firecracker.sh) to be
+> EXPERIMENTAL: Optionally run [`setup_kata_firecracker.sh`](setup_kata_firecracker.sh) to be
 able to use firecracker VMM with Kata.
 
 The firecracker setup switches the setup to use a sparse file backed loop device for
@@ -77,7 +77,7 @@ An example is
 
 ### Running Kata Workloads with Firecracker
 
-> EXPERIMENTAL: If firecracker setup has been enabled, runtime class set to "fire" will launch the POD/Deployment
+> EXPERIMENTAL: If firecracker setup has been enabled, runtime class set to "kata-fc" will launch the POD/Deployment
 with firecracker as the isolation mechanism for Kata.
 
 An example is

clr-k8s-examples/Vagrantfile

@@ -75,7 +75,7 @@ Vagrant.configure("2") do |config|
       # Bad hack for the vagrant libvirt boxes. WIll be removed once they are fixed.
       c.vm.provision "shell", privileged: false, inline: "sudo usermod --password vagrant root"
       c.vm.provision "shell", privileged: false, path: "setup_system.sh"
-      c.vm.provision "shell", privileged: false, path: "setup_firecracker.sh"
+      c.vm.provision "shell", privileged: false, path: "setup_kata_firecracker.sh"
     end
   end
 end

clr-k8s-examples/setup_kata_firecracker.sh

@@ -62,13 +62,13 @@ sudo systemctl enable --now devicemapper
 
 # For now till we address https://github.com/kubernetes-sigs/cri-o/issues/1991
 # use a shell script to expose firecracker through kata
-cat <<EOT | sudo tee /usr/bin/kata-runtime-fire
+cat <<EOT | sudo tee /usr/bin/kata-fc
 #!/bin/bash
 
 /usr/bin/kata-runtime --kata-config /etc/kata-containers/configuration_firecracker.toml "\$@"
 EOT
 
-sudo chmod +x /usr/bin/kata-runtime-fire
+sudo chmod +x /usr/bin/kata-fc
 
 # Add firecracker as a second runtime
 # Also setup crio to use devicemapper
@@ -76,8 +76,8 @@ sudo chmod +x /usr/bin/kata-runtime-fire
 sudo mkdir -p /etc/crio/
 sudo cp /usr/share/defaults/crio/crio.conf /etc/crio/crio.conf
 
-echo -e "\n[crio.runtime.runtimes.kata]\nruntime_path = \"/usr/bin/kata-runtime\"" | sudo tee -a /etc/crio/crio.conf
-echo -e "\n[crio.runtime.runtimes.fire]\nruntime_path = \"/usr/bin/kata-runtime-fire\"" | sudo tee -a /etc/crio/crio.conf
+echo -e "\n[crio.runtime.runtimes.kata-qemu]\nruntime_path = \"/usr/bin/kata-runtime\"" | sudo tee -a /etc/crio/crio.conf
+echo -e "\n[crio.runtime.runtimes.kata-fc]\nruntime_path = \"/usr/bin/kata-fc\"" | sudo tee -a /etc/crio/crio.conf
 
 sudo sed -i 's|\(\[crio\.runtime\]\)|\1\nmanage_network_ns_lifecycle = true|' /etc/crio/crio.conf
 

clr-k8s-examples/tests/test-deploy-fire.yaml

@@ -14,7 +14,7 @@ spec:
       labels:
         run: php-apache-fire
     spec:
-      runtimeClassName: fire
+      runtimeClassName: kata-fc
       containers:
       - image: k8s.gcr.io/hpa-example
         imagePullPolicy: Always