Este contenido no está disponible en el idioma seleccionado.
Chapter 9. DeploymentConfig [apps.openshift.io/v1]
- Description
Deployment Configs define the template for a pod and manages deploying new images or configuration changes. A single deployment configuration is usually analogous to a single micro-service. Can support many different deployment patterns, including full restart, customizable rolling updates, and fully custom behaviors, as well as pre- and post- deployment hooks. Each individual deployment is represented as a replication controller.
A deployment is "triggered" when its configuration is changed or a tag in an Image Stream is changed. Triggers can be disabled to allow manual control over a deployment. The "strategy" determines how the deployment is carried out and may be changed at any time. The
latestVersion
field is updated when a new deployment is triggered by any means.Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Deprecated: Use deployments or other means for declarative updates for pods instead.
- Type
-
object
- Required
-
spec
-
9.1. Specification
Property | Type | Description |
---|---|---|
|
| APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources |
|
| Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
| metadata is the standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| DeploymentConfigSpec represents the desired state of the deployment. |
|
| DeploymentConfigStatus represents the current deployment state. |
9.1.1. .spec
- Description
- DeploymentConfigSpec represents the desired state of the deployment.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| MinReadySeconds is the 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) |
|
| Paused indicates that the deployment config is paused resulting in no new deployments on template changes or changes in the template caused by other triggers. |
|
| Replicas is the number of desired replicas. |
|
| RevisionHistoryLimit is the number of old ReplicationControllers to retain to allow for rollbacks. This field is a pointer to allow for differentiation between an explicit zero and not specified. Defaults to 10. (This only applies to DeploymentConfigs created via the new group API resource, not the legacy resource.) |
|
| Selector is a label query over pods that should match the Replicas count. |
|
| DeploymentStrategy describes how to perform a deployment. |
| Template is the object that describes the pod that will be created if insufficient replicas are detected. | |
|
| Test ensures that this deployment config will have zero replicas except while a deployment is running. This allows the deployment config to be used as a continuous deployment test - triggering on images, running the deployment, and then succeeding or failing. Post strategy hooks and After actions can be used to integrate successful deployment with an action. |
|
| Triggers determine how updates to a DeploymentConfig result in new deployments. If no triggers are defined, a new deployment can only occur as a result of an explicit client update to the DeploymentConfig with a new LatestVersion. If null, defaults to having a config change trigger. |
|
| DeploymentTriggerPolicy describes a policy for a single trigger that results in a new deployment. |
9.1.2. .spec.strategy
- Description
- DeploymentStrategy describes how to perform a deployment.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| ActiveDeadlineSeconds is the duration in seconds that the deployer pods for this deployment config may be active on a node before the system actively tries to terminate them. |
|
| Annotations is a set of key, value pairs added to custom deployer and lifecycle pre/post hook pods. |
|
| CustomDeploymentStrategyParams are the input to the Custom deployment strategy. |
|
| Labels is a set of key, value pairs added to custom deployer and lifecycle pre/post hook pods. |
|
| RecreateDeploymentStrategyParams are the input to the Recreate deployment strategy. |
| Resources contains resource requirements to execute the deployment and any hooks. | |
|
| RollingDeploymentStrategyParams are the input to the Rolling deployment strategy. |
|
| Type is the name of a deployment strategy. |
9.1.3. .spec.strategy.customParams
- Description
- CustomDeploymentStrategyParams are the input to the Custom deployment strategy.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Command is optional and overrides CMD in the container Image. |
| Environment holds the environment which will be given to the container for Image. | |
|
| Image specifies a container image which can carry out a deployment. |
9.1.4. .spec.strategy.recreateParams
- Description
- RecreateDeploymentStrategyParams are the input to the Recreate deployment strategy.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| LifecycleHook defines a specific deployment lifecycle action. Only one type of action may be specified at any time. |
|
| LifecycleHook defines a specific deployment lifecycle action. Only one type of action may be specified at any time. |
|
| LifecycleHook defines a specific deployment lifecycle action. Only one type of action may be specified at any time. |
|
| TimeoutSeconds is the time to wait for updates before giving up. If the value is nil, a default will be used. |
9.1.5. .spec.strategy.recreateParams.mid
- Description
- LifecycleHook defines a specific deployment lifecycle action. Only one type of action may be specified at any time.
- Type
-
object
- Required
-
failurePolicy
-
Property | Type | Description |
---|---|---|
|
| ExecNewPodHook is a hook implementation which runs a command in a new pod based on the specified container which is assumed to be part of the deployment template. |
|
| FailurePolicy specifies what action to take if the hook fails. |
|
| TagImages instructs the deployer to tag the current image referenced under a container onto an image stream tag. |
|
| TagImageHook is a request to tag the image in a particular container onto an ImageStreamTag. |
9.1.6. .spec.strategy.recreateParams.mid.execNewPod
- Description
- ExecNewPodHook is a hook implementation which runs a command in a new pod based on the specified container which is assumed to be part of the deployment template.
- Type
-
object
- Required
-
command
-
containerName
-
Property | Type | Description |
---|---|---|
|
| Command is the action command and its arguments. |
|
| ContainerName is the name of a container in the deployment pod template whose container image will be used for the hook pod’s container. |
| Env is a set of environment variables to supply to the hook pod’s container. | |
|
| Volumes is a list of named volumes from the pod template which should be copied to the hook pod. Volumes names not found in pod spec are ignored. An empty list means no volumes will be copied. |
9.1.7. .spec.strategy.recreateParams.mid.tagImages
- Description
- TagImages instructs the deployer to tag the current image referenced under a container onto an image stream tag.
- Type
-
array
9.1.8. .spec.strategy.recreateParams.mid.tagImages[]
- Description
- TagImageHook is a request to tag the image in a particular container onto an ImageStreamTag.
- Type
-
object
- Required
-
containerName
-
to
-
Property | Type | Description |
---|---|---|
|
| ContainerName is the name of a container in the deployment config whose image value will be used as the source of the tag. If there is only a single container this value will be defaulted to the name of that container. |
| To is the target ImageStreamTag to set the container’s image onto. |
9.1.9. .spec.strategy.recreateParams.post
- Description
- LifecycleHook defines a specific deployment lifecycle action. Only one type of action may be specified at any time.
- Type
-
object
- Required
-
failurePolicy
-
Property | Type | Description |
---|---|---|
|
| ExecNewPodHook is a hook implementation which runs a command in a new pod based on the specified container which is assumed to be part of the deployment template. |
|
| FailurePolicy specifies what action to take if the hook fails. |
|
| TagImages instructs the deployer to tag the current image referenced under a container onto an image stream tag. |
|
| TagImageHook is a request to tag the image in a particular container onto an ImageStreamTag. |
9.1.10. .spec.strategy.recreateParams.post.execNewPod
- Description
- ExecNewPodHook is a hook implementation which runs a command in a new pod based on the specified container which is assumed to be part of the deployment template.
- Type
-
object
- Required
-
command
-
containerName
-
Property | Type | Description |
---|---|---|
|
| Command is the action command and its arguments. |
|
| ContainerName is the name of a container in the deployment pod template whose container image will be used for the hook pod’s container. |
| Env is a set of environment variables to supply to the hook pod’s container. | |
|
| Volumes is a list of named volumes from the pod template which should be copied to the hook pod. Volumes names not found in pod spec are ignored. An empty list means no volumes will be copied. |
9.1.11. .spec.strategy.recreateParams.post.tagImages
- Description
- TagImages instructs the deployer to tag the current image referenced under a container onto an image stream tag.
- Type
-
array
9.1.12. .spec.strategy.recreateParams.post.tagImages[]
- Description
- TagImageHook is a request to tag the image in a particular container onto an ImageStreamTag.
- Type
-
object
- Required
-
containerName
-
to
-
Property | Type | Description |
---|---|---|
|
| ContainerName is the name of a container in the deployment config whose image value will be used as the source of the tag. If there is only a single container this value will be defaulted to the name of that container. |
| To is the target ImageStreamTag to set the container’s image onto. |
9.1.13. .spec.strategy.recreateParams.pre
- Description
- LifecycleHook defines a specific deployment lifecycle action. Only one type of action may be specified at any time.
- Type
-
object
- Required
-
failurePolicy
-
Property | Type | Description |
---|---|---|
|
| ExecNewPodHook is a hook implementation which runs a command in a new pod based on the specified container which is assumed to be part of the deployment template. |
|
| FailurePolicy specifies what action to take if the hook fails. |
|
| TagImages instructs the deployer to tag the current image referenced under a container onto an image stream tag. |
|
| TagImageHook is a request to tag the image in a particular container onto an ImageStreamTag. |
9.1.14. .spec.strategy.recreateParams.pre.execNewPod
- Description
- ExecNewPodHook is a hook implementation which runs a command in a new pod based on the specified container which is assumed to be part of the deployment template.
- Type
-
object
- Required
-
command
-
containerName
-
Property | Type | Description |
---|---|---|
|
| Command is the action command and its arguments. |
|
| ContainerName is the name of a container in the deployment pod template whose container image will be used for the hook pod’s container. |
| Env is a set of environment variables to supply to the hook pod’s container. | |
|
| Volumes is a list of named volumes from the pod template which should be copied to the hook pod. Volumes names not found in pod spec are ignored. An empty list means no volumes will be copied. |
9.1.15. .spec.strategy.recreateParams.pre.tagImages
- Description
- TagImages instructs the deployer to tag the current image referenced under a container onto an image stream tag.
- Type
-
array
9.1.16. .spec.strategy.recreateParams.pre.tagImages[]
- Description
- TagImageHook is a request to tag the image in a particular container onto an ImageStreamTag.
- Type
-
object
- Required
-
containerName
-
to
-
Property | Type | Description |
---|---|---|
|
| ContainerName is the name of a container in the deployment config whose image value will be used as the source of the tag. If there is only a single container this value will be defaulted to the name of that container. |
| To is the target ImageStreamTag to set the container’s image onto. |
9.1.17. .spec.strategy.rollingParams
- Description
- RollingDeploymentStrategyParams are the input to the Rolling deployment strategy.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| IntervalSeconds is the time to wait between polling deployment status after update. If the value is nil, a default will be used. |
| MaxSurge is the maximum number of pods that can be scheduled above the original number of pods. Value can be an absolute number (ex: 5) or a percentage of total pods at the start of the update (ex: 10%). Absolute number is calculated from percentage by rounding up. This cannot be 0 if MaxUnavailable is 0. By default, 25% is used. Example: when this is set to 30%, the new RC can be scaled up by 30% immediately when the rolling update starts. Once old pods have been killed, new RC can be scaled up further, ensuring that total number of pods running at any time during the update is atmost 130% of original pods. | |
| MaxUnavailable is the maximum number of pods that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of total pods at the start of update (ex: 10%). Absolute number is calculated from percentage by rounding down. This cannot be 0 if MaxSurge is 0. By default, 25% is used. Example: when this is set to 30%, the old RC can be scaled down by 30% immediately when the rolling update starts. Once new pods are ready, old RC can be scaled down further, followed by scaling up the new RC, ensuring that at least 70% of original number of pods are available at all times during the update. | |
|
| LifecycleHook defines a specific deployment lifecycle action. Only one type of action may be specified at any time. |
|
| LifecycleHook defines a specific deployment lifecycle action. Only one type of action may be specified at any time. |
|
| TimeoutSeconds is the time to wait for updates before giving up. If the value is nil, a default will be used. |
|
| UpdatePeriodSeconds is the time to wait between individual pod updates. If the value is nil, a default will be used. |
9.1.18. .spec.strategy.rollingParams.post
- Description
- LifecycleHook defines a specific deployment lifecycle action. Only one type of action may be specified at any time.
- Type
-
object
- Required
-
failurePolicy
-
Property | Type | Description |
---|---|---|
|
| ExecNewPodHook is a hook implementation which runs a command in a new pod based on the specified container which is assumed to be part of the deployment template. |
|
| FailurePolicy specifies what action to take if the hook fails. |
|
| TagImages instructs the deployer to tag the current image referenced under a container onto an image stream tag. |
|
| TagImageHook is a request to tag the image in a particular container onto an ImageStreamTag. |
9.1.19. .spec.strategy.rollingParams.post.execNewPod
- Description
- ExecNewPodHook is a hook implementation which runs a command in a new pod based on the specified container which is assumed to be part of the deployment template.
- Type
-
object
- Required
-
command
-
containerName
-
Property | Type | Description |
---|---|---|
|
| Command is the action command and its arguments. |
|
| ContainerName is the name of a container in the deployment pod template whose container image will be used for the hook pod’s container. |
| Env is a set of environment variables to supply to the hook pod’s container. | |
|
| Volumes is a list of named volumes from the pod template which should be copied to the hook pod. Volumes names not found in pod spec are ignored. An empty list means no volumes will be copied. |
9.1.20. .spec.strategy.rollingParams.post.tagImages
- Description
- TagImages instructs the deployer to tag the current image referenced under a container onto an image stream tag.
- Type
-
array
9.1.21. .spec.strategy.rollingParams.post.tagImages[]
- Description
- TagImageHook is a request to tag the image in a particular container onto an ImageStreamTag.
- Type
-
object
- Required
-
containerName
-
to
-
Property | Type | Description |
---|---|---|
|
| ContainerName is the name of a container in the deployment config whose image value will be used as the source of the tag. If there is only a single container this value will be defaulted to the name of that container. |
| To is the target ImageStreamTag to set the container’s image onto. |
9.1.22. .spec.strategy.rollingParams.pre
- Description
- LifecycleHook defines a specific deployment lifecycle action. Only one type of action may be specified at any time.
- Type
-
object
- Required
-
failurePolicy
-
Property | Type | Description |
---|---|---|
|
| ExecNewPodHook is a hook implementation which runs a command in a new pod based on the specified container which is assumed to be part of the deployment template. |
|
| FailurePolicy specifies what action to take if the hook fails. |
|
| TagImages instructs the deployer to tag the current image referenced under a container onto an image stream tag. |
|
| TagImageHook is a request to tag the image in a particular container onto an ImageStreamTag. |
9.1.23. .spec.strategy.rollingParams.pre.execNewPod
- Description
- ExecNewPodHook is a hook implementation which runs a command in a new pod based on the specified container which is assumed to be part of the deployment template.
- Type
-
object
- Required
-
command
-
containerName
-
Property | Type | Description |
---|---|---|
|
| Command is the action command and its arguments. |
|
| ContainerName is the name of a container in the deployment pod template whose container image will be used for the hook pod’s container. |
| Env is a set of environment variables to supply to the hook pod’s container. | |
|
| Volumes is a list of named volumes from the pod template which should be copied to the hook pod. Volumes names not found in pod spec are ignored. An empty list means no volumes will be copied. |
9.1.24. .spec.strategy.rollingParams.pre.tagImages
- Description
- TagImages instructs the deployer to tag the current image referenced under a container onto an image stream tag.
- Type
-
array
9.1.25. .spec.strategy.rollingParams.pre.tagImages[]
- Description
- TagImageHook is a request to tag the image in a particular container onto an ImageStreamTag.
- Type
-
object
- Required
-
containerName
-
to
-
Property | Type | Description |
---|---|---|
|
| ContainerName is the name of a container in the deployment config whose image value will be used as the source of the tag. If there is only a single container this value will be defaulted to the name of that container. |
| To is the target ImageStreamTag to set the container’s image onto. |
9.1.26. .spec.triggers
- Description
- Triggers determine how updates to a DeploymentConfig result in new deployments. If no triggers are defined, a new deployment can only occur as a result of an explicit client update to the DeploymentConfig with a new LatestVersion. If null, defaults to having a config change trigger.
- Type
-
array
9.1.27. .spec.triggers[]
- Description
- DeploymentTriggerPolicy describes a policy for a single trigger that results in a new deployment.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| DeploymentTriggerImageChangeParams represents the parameters to the ImageChange trigger. |
|
| Type of the trigger |
9.1.28. .spec.triggers[].imageChangeParams
- Description
- DeploymentTriggerImageChangeParams represents the parameters to the ImageChange trigger.
- Type
-
object
- Required
-
from
-
Property | Type | Description |
---|---|---|
|
| Automatic means that the detection of a new tag value should result in an image update inside the pod template. |
|
| ContainerNames is used to restrict tag updates to the specified set of container names in a pod. If multiple triggers point to the same containers, the resulting behavior is undefined. Future API versions will make this a validation error. If ContainerNames does not point to a valid container, the trigger will be ignored. Future API versions will make this a validation error. |
| From is a reference to an image stream tag to watch for changes. From.Name is the only required subfield - if From.Namespace is blank, the namespace of the current deployment trigger will be used. | |
|
| LastTriggeredImage is the last image to be triggered. |
9.1.29. .status
- Description
- DeploymentConfigStatus represents the current deployment state.
- Type
-
object
- Required
-
latestVersion
-
observedGeneration
-
replicas
-
updatedReplicas
-
availableReplicas
-
unavailableReplicas
-
Property | Type | Description |
---|---|---|
|
| AvailableReplicas is the total number of available pods targeted by this deployment config. |
|
| Conditions represents the latest available observations of a deployment config’s current state. |
|
| DeploymentCondition describes the state of a deployment config at a certain point. |
|
| DeploymentDetails captures information about the causes of a deployment. |
|
| LatestVersion is used to determine whether the current deployment associated with a deployment config is out of sync. |
|
| ObservedGeneration is the most recent generation observed by the deployment config controller. |
|
| Total number of ready pods targeted by this deployment. |
|
| Replicas is the total number of pods targeted by this deployment config. |
|
| UnavailableReplicas is the total number of unavailable pods targeted by this deployment config. |
|
| UpdatedReplicas is the total number of non-terminated pods targeted by this deployment config that have the desired template spec. |
9.1.30. .status.conditions
- Description
- Conditions represents the latest available observations of a deployment config’s current state.
- Type
-
array
9.1.31. .status.conditions[]
- Description
- DeploymentCondition describes the state of a deployment config at a certain point.
- Type
-
object
- Required
-
type
-
status
-
Property | Type | Description |
---|---|---|
| The last time the condition transitioned from one status to another. | |
| The last time this condition was updated. | |
|
| A human readable message indicating details about the transition. |
|
| The reason for the condition’s last transition. |
|
| Status of the condition, one of True, False, Unknown. |
|
| Type of deployment condition. |
9.1.32. .status.details
- Description
- DeploymentDetails captures information about the causes of a deployment.
- Type
-
object
- Required
-
causes
-
Property | Type | Description |
---|---|---|
|
| Causes are extended data associated with all the causes for creating a new deployment |
|
| DeploymentCause captures information about a particular cause of a deployment. |
|
| Message is the user specified change message, if this deployment was triggered manually by the user |
9.1.33. .status.details.causes
- Description
- Causes are extended data associated with all the causes for creating a new deployment
- Type
-
array
9.1.34. .status.details.causes[]
- Description
- DeploymentCause captures information about a particular cause of a deployment.
- Type
-
object
- Required
-
type
-
Property | Type | Description |
---|---|---|
|
| DeploymentCauseImageTrigger represents details about the cause of a deployment originating from an image change trigger |
|
| Type of the trigger that resulted in the creation of a new deployment |
9.1.35. .status.details.causes[].imageTrigger
- Description
- DeploymentCauseImageTrigger represents details about the cause of a deployment originating from an image change trigger
- Type
-
object
- Required
-
from
-
Property | Type | Description |
---|---|---|
| From is a reference to the changed object which triggered a deployment. The field may have the kinds DockerImage, ImageStreamTag, or ImageStreamImage. |
9.2. API endpoints
The following API endpoints are available:
/apis/apps.openshift.io/v1/deploymentconfigs
-
GET
: list or watch objects of kind DeploymentConfig
-
/apis/apps.openshift.io/v1/watch/deploymentconfigs
-
GET
: watch individual changes to a list of DeploymentConfig. deprecated: use the 'watch' parameter with a list operation instead.
-
/apis/apps.openshift.io/v1/namespaces/{namespace}/deploymentconfigs
-
DELETE
: delete collection of DeploymentConfig -
GET
: list or watch objects of kind DeploymentConfig -
POST
: create a DeploymentConfig
-
/apis/apps.openshift.io/v1/watch/namespaces/{namespace}/deploymentconfigs
-
GET
: watch individual changes to a list of DeploymentConfig. deprecated: use the 'watch' parameter with a list operation instead.
-
/apis/apps.openshift.io/v1/namespaces/{namespace}/deploymentconfigs/{name}
-
DELETE
: delete a DeploymentConfig -
GET
: read the specified DeploymentConfig -
PATCH
: partially update the specified DeploymentConfig -
PUT
: replace the specified DeploymentConfig
-
/apis/apps.openshift.io/v1/watch/namespaces/{namespace}/deploymentconfigs/{name}
-
GET
: watch changes to an object of kind DeploymentConfig. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
-
/apis/apps.openshift.io/v1/namespaces/{namespace}/deploymentconfigs/{name}/status
-
GET
: read status of the specified DeploymentConfig -
PATCH
: partially update status of the specified DeploymentConfig -
PUT
: replace status of the specified DeploymentConfig
-
9.2.1. /apis/apps.openshift.io/v1/deploymentconfigs
- HTTP method
-
GET
- Description
- list or watch objects of kind DeploymentConfig
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
9.2.2. /apis/apps.openshift.io/v1/watch/deploymentconfigs
- HTTP method
-
GET
- Description
- watch individual changes to a list of DeploymentConfig. deprecated: use the 'watch' parameter with a list operation instead.
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
9.2.3. /apis/apps.openshift.io/v1/namespaces/{namespace}/deploymentconfigs
- HTTP method
-
DELETE
- Description
- delete collection of DeploymentConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list or watch objects of kind DeploymentConfig
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a DeploymentConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
9.2.4. /apis/apps.openshift.io/v1/watch/namespaces/{namespace}/deploymentconfigs
- HTTP method
-
GET
- Description
- watch individual changes to a list of DeploymentConfig. deprecated: use the 'watch' parameter with a list operation instead.
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
9.2.5. /apis/apps.openshift.io/v1/namespaces/{namespace}/deploymentconfigs/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the DeploymentConfig |
- HTTP method
-
DELETE
- Description
- delete a DeploymentConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
HTTP code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified DeploymentConfig
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified DeploymentConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified DeploymentConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
9.2.6. /apis/apps.openshift.io/v1/watch/namespaces/{namespace}/deploymentconfigs/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the DeploymentConfig |
- HTTP method
-
GET
- Description
- watch changes to an object of kind DeploymentConfig. deprecated: use the 'watch' parameter with a list operation instead, filtered to a single item with the 'fieldSelector' parameter.
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
9.2.7. /apis/apps.openshift.io/v1/namespaces/{namespace}/deploymentconfigs/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the DeploymentConfig |
- HTTP method
-
GET
- Description
- read status of the specified DeploymentConfig
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified DeploymentConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified DeploymentConfig
Parameter | Type | Description |
---|---|---|
|
| When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed |
|
| fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |