@jkcfg/kubernetes/schemas/v1.5.0-local/deploymentspec.json

jk Kubernetes library

{
  "$schema": "http://json-schema.org/schema#", 
  "required": [
    "template"
  ], 
  "type": "object", 
  "description": "DeploymentSpec is the specification of the desired behavior of the Deployment.", 
  "properties": {
    "selector": {
      "description": "Label selector for pods. Existing ReplicaSets whose pods are selected by this will be the ones affected by this deployment.", 
      "$ref": "_definitions.json#/definitions/unversioned.LabelSelector"
    }, 
    "replicas": {
      "type": "integer", 
      "description": "Number of desired pods. This is a pointer to distinguish between explicit zero and not specified. Defaults to 1.", 
      "format": "int32"
    }, 
    "strategy": {
      "description": "The deployment strategy to use to replace existing pods with new ones.", 
      "$ref": "_definitions.json#/definitions/v1beta1.DeploymentStrategy"
    }, 
    "paused": {
      "type": "boolean", 
      "description": "Indicates that the deployment is paused and will not be processed by the deployment controller."
    }, 
    "rollbackTo": {
      "description": "The config this deployment is rolling back to. Will be cleared after rollback is done.", 
      "$ref": "_definitions.json#/definitions/v1beta1.RollbackConfig"
    }, 
    "template": {
      "description": "Template describes the pods that will be created.", 
      "$ref": "_definitions.json#/definitions/v1.PodTemplateSpec"
    }, 
    "revisionHistoryLimit": {
      "type": "integer", 
      "description": "The number of old ReplicaSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified.", 
      "format": "int32"
    }, 
    "progressDeadlineSeconds": {
      "type": "integer", 
      "description": "The maximum time in seconds for a deployment to make progress before it is considered to be failed. The deployment controller will continue to process failed deployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the deployment status. Once autoRollback is implemented, the deployment controller will automatically rollback failed deployments. Note that progress will not be estimated during the time a deployment is paused. This is not set by default.", 
      "format": "int32"
    }, 
    "minReadySeconds": {
      "type": "integer", 
      "description": "Minimum number of seconds for which a newly created pod should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (pod will be considered available as soon as it is ready)", 
      "format": "int32"
    }
  }
}