Argo Workflows Io K8S Api Core V1 Storage Os Volume Source Structure

{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/argo-workflows/refs/heads/main/json-structure/argo-workflows-io-k8s-api-core-v1-storage-os-volume-source-structure.json",
  "name": "io.k8s.api.core.v1.StorageOSVolumeSource",
  "description": "Represents a StorageOS persistent volume resource.",
  "type": "object",
  "properties": {
    "fsType": {
      "description": "fsType is the filesystem type to mount. Must be a filesystem type supported by the host operating system. Ex. \"ext4\", \"xfs\", \"ntfs\". Implicitly inferred to be \"ext4\" if unspecified.",
      "type": "string"
    },
    "readOnly": {
      "description": "readOnly defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.",
      "type": "boolean"
    },
    "secretRef": {
      "description": "secretRef specifies the secret to use for obtaining the StorageOS API credentials.  If not specified, default values will be attempted.",
      "$ref": "#/definitions/io.k8s.api.core.v1.LocalObjectReference"
    },
    "volumeName": {
      "description": "volumeName is the human-readable name of the StorageOS volume.  Volume names are only unique within a namespace.",
      "type": "string"
    },
    "volumeNamespace": {
      "description": "volumeNamespace specifies the scope of the volume within StorageOS.  If no namespace is specified then the Pod's namespace will be used.  This allows the Kubernetes name scoping to be mirrored within StorageOS for tighter integration. Set VolumeName to any name to override the default behaviour. Set to \"default\" if you are not using namespaces within StorageOS. Namespaces that do not pre-exist within StorageOS will be created.",
      "type": "string"
    }
  }
}