Skip to content

Commit

Permalink
Adding new schemas
Browse files Browse the repository at this point in the history
  • Loading branch information
jacksoncage committed Aug 23, 2023
1 parent 7f82a2c commit 83ef81b
Show file tree
Hide file tree
Showing 156 changed files with 571 additions and 4,226 deletions.
22 changes: 21 additions & 1 deletion master-local/_definitions.json
Original file line number Diff line number Diff line change
Expand Up @@ -8177,7 +8177,7 @@
"description": "dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef\n allows any non-core object, as well as PersistentVolumeClaim objects.\n* While dataSource ignores disallowed values (dropping them), dataSourceRef\n preserves all values, and generates an error if a disallowed value is\n specified.\n* While dataSource only allows local objects, dataSourceRef allows objects\n in any namespaces.\n(Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled."
},
"resources": {
"$ref": "#/definitions/io.k8s.api.core.v1.ResourceRequirements",
"$ref": "#/definitions/io.k8s.api.core.v1.VolumeResourceRequirements",
"description": "resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources"
},
"selector": {
Expand Down Expand Up @@ -11164,6 +11164,26 @@
},
"type": "object"
},
"io.k8s.api.core.v1.VolumeResourceRequirements": {
"description": "VolumeResourceRequirements describes the storage resource requirements for a volume.",
"properties": {
"limits": {
"additionalProperties": {
"$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
},
"description": "Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
"type": "object"
},
"requests": {
"additionalProperties": {
"$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
},
"description": "Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
"type": "object"
}
},
"type": "object"
},
"io.k8s.api.core.v1.VsphereVirtualDiskVolumeSource": {
"description": "Represents a vSphere volume resource.",
"properties": {
Expand Down
3 changes: 3 additions & 0 deletions master-local/all.json
Original file line number Diff line number Diff line change
Expand Up @@ -1080,6 +1080,9 @@
{
"$ref": "_definitions.json#/definitions/io.k8s.api.core.v1.VolumeProjection"
},
{
"$ref": "_definitions.json#/definitions/io.k8s.api.core.v1.VolumeResourceRequirements"
},
{
"$ref": "_definitions.json#/definitions/io.k8s.api.core.v1.VsphereVirtualDiskVolumeSource"
},
Expand Down
2 changes: 1 addition & 1 deletion master-local/persistentvolumeclaimspec-v1.json
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
"description": "dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef\n allows any non-core object, as well as PersistentVolumeClaim objects.\n* While dataSource ignores disallowed values (dropping them), dataSourceRef\n preserves all values, and generates an error if a disallowed value is\n specified.\n* While dataSource only allows local objects, dataSourceRef allows objects\n in any namespaces.\n(Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled."
},
"resources": {
"$ref": "_definitions.json#/definitions/io.k8s.api.core.v1.ResourceRequirements",
"$ref": "_definitions.json#/definitions/io.k8s.api.core.v1.VolumeResourceRequirements",
"description": "resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources"
},
"selector": {
Expand Down
2 changes: 1 addition & 1 deletion master-local/persistentvolumeclaimspec.json
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
"description": "dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef\n allows any non-core object, as well as PersistentVolumeClaim objects.\n* While dataSource ignores disallowed values (dropping them), dataSourceRef\n preserves all values, and generates an error if a disallowed value is\n specified.\n* While dataSource only allows local objects, dataSourceRef allows objects\n in any namespaces.\n(Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled."
},
"resources": {
"$ref": "_definitions.json#/definitions/io.k8s.api.core.v1.ResourceRequirements",
"$ref": "_definitions.json#/definitions/io.k8s.api.core.v1.VolumeResourceRequirements",
"description": "resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources"
},
"selector": {
Expand Down
27 changes: 27 additions & 0 deletions master-local/volumeresourcerequirements-v1.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
{
"description": "VolumeResourceRequirements describes the storage resource requirements for a volume.",
"properties": {
"limits": {
"additionalProperties": {
"$ref": "_definitions.json#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
},
"description": "Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
"type": [
"object",
"null"
]
},
"requests": {
"additionalProperties": {
"$ref": "_definitions.json#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
},
"description": "Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
"type": [
"object",
"null"
]
}
},
"type": "object",
"$schema": "http://json-schema.org/schema#"
}
27 changes: 27 additions & 0 deletions master-local/volumeresourcerequirements.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
{
"description": "VolumeResourceRequirements describes the storage resource requirements for a volume.",
"properties": {
"limits": {
"additionalProperties": {
"$ref": "_definitions.json#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
},
"description": "Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
"type": [
"object",
"null"
]
},
"requests": {
"additionalProperties": {
"$ref": "_definitions.json#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
},
"description": "Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
"type": [
"object",
"null"
]
}
},
"type": "object",
"$schema": "http://json-schema.org/schema#"
}
23 changes: 22 additions & 1 deletion master-standalone-strict/_definitions.json
Original file line number Diff line number Diff line change
Expand Up @@ -8449,7 +8449,7 @@
"description": "dataSourceRef specifies the object from which to populate the volume with data, if a non-empty volume is desired. This may be any object from a non-empty API group (non core object) or a PersistentVolumeClaim object. When this field is specified, volume binding will only succeed if the type of the specified object matches some installed volume populator or dynamic provisioner. This field will replace the functionality of the dataSource field and as such if both fields are non-empty, they must have the same value. For backwards compatibility, when namespace isn't specified in dataSourceRef, both fields (dataSource and dataSourceRef) will be set to the same value automatically if one of them is empty and the other is non-empty. When namespace is specified in dataSourceRef, dataSource isn't set to the same value and must be empty. There are three important differences between dataSource and dataSourceRef: * While dataSource only allows two specific types of objects, dataSourceRef\n allows any non-core object, as well as PersistentVolumeClaim objects.\n* While dataSource ignores disallowed values (dropping them), dataSourceRef\n preserves all values, and generates an error if a disallowed value is\n specified.\n* While dataSource only allows local objects, dataSourceRef allows objects\n in any namespaces.\n(Beta) Using this field requires the AnyVolumeDataSource feature gate to be enabled. (Alpha) Using the namespace field of dataSourceRef requires the CrossNamespaceVolumeDataSource feature gate to be enabled."
},
"resources": {
"$ref": "#/definitions/io.k8s.api.core.v1.ResourceRequirements",
"$ref": "#/definitions/io.k8s.api.core.v1.VolumeResourceRequirements",
"description": "resources represents the minimum resources the volume should have. If RecoverVolumeExpansionFailure feature is enabled users are allowed to specify resource requirements that are lower than previous value but must still be higher than capacity recorded in the status field of the claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources"
},
"selector": {
Expand Down Expand Up @@ -11523,6 +11523,27 @@
"type": "object",
"additionalProperties": false
},
"io.k8s.api.core.v1.VolumeResourceRequirements": {
"description": "VolumeResourceRequirements describes the storage resource requirements for a volume.",
"properties": {
"limits": {
"additionalProperties": {
"$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
},
"description": "Limits describes the maximum amount of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
"type": "object"
},
"requests": {
"additionalProperties": {
"$ref": "#/definitions/io.k8s.apimachinery.pkg.api.resource.Quantity"
},
"description": "Requests describes the minimum amount of compute resources required. If Requests is omitted for a container, it defaults to Limits if that is explicitly specified, otherwise to an implementation-defined value. Requests cannot exceed Limits. More info: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/",
"type": "object"
}
},
"type": "object",
"additionalProperties": false
},
"io.k8s.api.core.v1.VsphereVirtualDiskVolumeSource": {
"description": "Represents a vSphere volume resource.",
"properties": {
Expand Down
3 changes: 3 additions & 0 deletions master-standalone-strict/all.json
Original file line number Diff line number Diff line change
Expand Up @@ -1080,6 +1080,9 @@
{
"$ref": "_definitions.json#/definitions/io.k8s.api.core.v1.VolumeProjection"
},
{
"$ref": "_definitions.json#/definitions/io.k8s.api.core.v1.VolumeResourceRequirements"
},
{
"$ref": "_definitions.json#/definitions/io.k8s.api.core.v1.VsphereVirtualDiskVolumeSource"
},
Expand Down
30 changes: 1 addition & 29 deletions master-standalone-strict/cronjob-batch-v1.json
Original file line number Diff line number Diff line change
Expand Up @@ -9108,36 +9108,8 @@
"additionalProperties": false
},
"resources": {
"description": "ResourceRequirements describes the compute resource requirements.",
"description": "VolumeResourceRequirements describes the storage resource requirements for a volume.",
"properties": {
"claims": {
"description": "Claims lists the names of resources, defined in spec.resourceClaims, that are used by this container.\n\nThis is an alpha field and requires enabling the DynamicResourceAllocation feature gate.\n\nThis field is immutable. It can only be set for containers.",
"items": {
"description": "ResourceClaim references one entry in PodSpec.ResourceClaims.",
"properties": {
"name": {
"description": "Name must match the name of one entry in pod.spec.resourceClaims of the Pod where this field is used. It makes that resource available inside a container.",
"type": "string"
}
},
"required": [
"name"
],
"type": [
"object",
"null"
],
"additionalProperties": false
},
"type": [
"array",
"null"
],
"x-kubernetes-list-map-keys": [
"name"
],
"x-kubernetes-list-type": "map"
},
"limits": {
"additionalProperties": {
"oneOf": [
Expand Down
Loading

0 comments on commit 83ef81b

Please sign in to comment.