mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-09-17 15:13:08 +00:00
@@ -58134,6 +58134,31 @@
|
||||
}
|
||||
}
|
||||
},
|
||||
"io.k8s.api.core.v1.AzureFilePersistentVolumeSource": {
|
||||
"description": "AzureFile represents an Azure File Service mount on the host and bind mount to the pod.",
|
||||
"required": [
|
||||
"secretName",
|
||||
"shareName"
|
||||
],
|
||||
"properties": {
|
||||
"readOnly": {
|
||||
"description": "Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts.",
|
||||
"type": "boolean"
|
||||
},
|
||||
"secretName": {
|
||||
"description": "the name of secret that contains Azure Storage Account Name and Key",
|
||||
"type": "string"
|
||||
},
|
||||
"secretNamespace": {
|
||||
"description": "the namespace of the secret that contains Azure Storage Account Name and Key default is the same as the Pod",
|
||||
"type": "string"
|
||||
},
|
||||
"shareName": {
|
||||
"description": "Share Name",
|
||||
"type": "string"
|
||||
}
|
||||
}
|
||||
},
|
||||
"io.k8s.api.core.v1.AzureFileVolumeSource": {
|
||||
"description": "AzureFile represents an Azure File Service mount on the host and bind mount to the pod.",
|
||||
"required": [
|
||||
@@ -60429,7 +60454,7 @@
|
||||
},
|
||||
"azureFile": {
|
||||
"description": "AzureFile represents an Azure File Service mount on the host and bind mount to the pod.",
|
||||
"$ref": "#/definitions/io.k8s.api.core.v1.AzureFileVolumeSource"
|
||||
"$ref": "#/definitions/io.k8s.api.core.v1.AzureFilePersistentVolumeSource"
|
||||
},
|
||||
"capacity": {
|
||||
"description": "A description of the persistent volume's resources and capacity. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#capacity",
|
||||
|
@@ -18881,7 +18881,7 @@
|
||||
"description": "FlexVolume represents a generic volume resource that is provisioned/attached using an exec based plugin. This is an alpha feature and may change in future."
|
||||
},
|
||||
"azureFile": {
|
||||
"$ref": "v1.AzureFileVolumeSource",
|
||||
"$ref": "v1.AzureFilePersistentVolumeSource",
|
||||
"description": "AzureFile represents an Azure File Service mount on the host and bind mount to the pod."
|
||||
},
|
||||
"vsphereVolume": {
|
||||
@@ -19301,12 +19301,13 @@
|
||||
}
|
||||
}
|
||||
},
|
||||
"v1.AzureFileVolumeSource": {
|
||||
"id": "v1.AzureFileVolumeSource",
|
||||
"v1.AzureFilePersistentVolumeSource": {
|
||||
"id": "v1.AzureFilePersistentVolumeSource",
|
||||
"description": "AzureFile represents an Azure File Service mount on the host and bind mount to the pod.",
|
||||
"required": [
|
||||
"secretName",
|
||||
"shareName"
|
||||
"shareName",
|
||||
"secretNamespace"
|
||||
],
|
||||
"properties": {
|
||||
"secretName": {
|
||||
@@ -19320,6 +19321,10 @@
|
||||
"readOnly": {
|
||||
"type": "boolean",
|
||||
"description": "Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts."
|
||||
},
|
||||
"secretNamespace": {
|
||||
"type": "string",
|
||||
"description": "the namespace of the secret that contains Azure Storage Account Name and Key default is the same as the Pod"
|
||||
}
|
||||
}
|
||||
},
|
||||
@@ -20054,6 +20059,28 @@
|
||||
}
|
||||
}
|
||||
},
|
||||
"v1.AzureFileVolumeSource": {
|
||||
"id": "v1.AzureFileVolumeSource",
|
||||
"description": "AzureFile represents an Azure File Service mount on the host and bind mount to the pod.",
|
||||
"required": [
|
||||
"secretName",
|
||||
"shareName"
|
||||
],
|
||||
"properties": {
|
||||
"secretName": {
|
||||
"type": "string",
|
||||
"description": "the name of secret that contains Azure Storage Account Name and Key"
|
||||
},
|
||||
"shareName": {
|
||||
"type": "string",
|
||||
"description": "Share Name"
|
||||
},
|
||||
"readOnly": {
|
||||
"type": "boolean",
|
||||
"description": "Defaults to false (read/write). ReadOnly here will force the ReadOnly setting in VolumeMounts."
|
||||
}
|
||||
}
|
||||
},
|
||||
"v1.ConfigMapVolumeSource": {
|
||||
"id": "v1.ConfigMapVolumeSource",
|
||||
"description": "Adapts a ConfigMap into a volume.\n\nThe contents of the target ConfigMap's Data field will be presented in a volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. ConfigMap volumes support ownership management and SELinux relabeling.",
|
||||
|
Reference in New Issue
Block a user