diff --git a/Charts/ioc-instance/values.yaml b/Charts/ioc-instance/values.yaml
index 318a757..b6b9ea7 100644
--- a/Charts/ioc-instance/values.yaml
+++ b/Charts/ioc-instance/values.yaml
@@ -24,7 +24,7 @@ location: ""
 ioc_group: ""
 
 # Features relating to the pod run time, such as USB devices
-runtimeClassName: {}
+runtimeClassName: ""
 
 
 # we use the default service account in the namespace so leave this out
diff --git a/Schemas/ioc-instance.schema.json b/Schemas/ioc-instance.schema.json
index ccb0b07..ab84fe5 100644
--- a/Schemas/ioc-instance.schema.json
+++ b/Schemas/ioc-instance.schema.json
@@ -112,8 +112,7 @@
           "$ref": "https://kubernetesjsonschema.dev/v1.18.1/_definitions.json#/definitions/io.k8s.api.core.v1.Container/properties/resources"
         },
         "runtimeClassName": {
-          "type": "object",
-          "description":"RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are (currently) manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod.  For more details, see https://git.k8s.io/enhancements/keps/sig-node/runtime-class.md"
+          "$ref": "https://kubernetesjsonschema.dev/v1.18.1/_definitions.json#/definitions/io.k8s.api.core.v1.PodSpec/properties/runtimeClassName"
         },
         "nodeName": {
           "$ref": "https://kubernetesjsonschema.dev/v1.18.1/_definitions.json#/definitions/io.k8s.api.core.v1.PodSpec/properties/nodeName"