Chapter 10. DeploymentConfigRollback [apps.openshift.io/v1]
- Description
DeploymentConfigRollback provides the input to rollback generation.
Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).
- Type
-
object - Required
-
name -
spec
-
10.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 |
|
|
| Name of the deployment config that will be rolled back. |
|
|
| DeploymentConfigRollbackSpec represents the options for rollback generation. |
|
|
| UpdatedAnnotations is a set of new annotations that will be added in the deployment config. |
10.1.1. .spec
- Description
- DeploymentConfigRollbackSpec represents the options for rollback generation.
- Type
-
object - Required
-
from -
includeTriggers -
includeTemplate -
includeReplicationMeta -
includeStrategy
-
| Property | Type | Description |
|---|---|---|
|
| From points to a ReplicationController which is a deployment. | |
|
|
| IncludeReplicationMeta specifies whether to include the replica count and selector. |
|
|
| IncludeStrategy specifies whether to include the deployment Strategy. |
|
|
| IncludeTemplate specifies whether to include the PodTemplateSpec. |
|
|
| IncludeTriggers specifies whether to include config Triggers. |
|
|
| Revision to rollback to. If set to 0, rollback to the last revision. |
10.2. API endpoints
The following API endpoints are available:
/apis/apps.openshift.io/v1/namespaces/{namespace}/deploymentconfigs/{name}/rollback-
POST: create rollback of a DeploymentConfig
-
10.2.1. /apis/apps.openshift.io/v1/namespaces/{namespace}/deploymentconfigs/{name}/rollback
| Parameter | Type | Description |
|---|---|---|
|
|
| name of the DeploymentConfigRollback |
|
|
| object name and auth scope, such as for teams and projects |
| 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 |
|
|
| fieldManager is a name associated with the actor or entity that is making these changes. The value must be less than or 128 characters long, and only contain printable characters, as defined by https://golang.org/pkg/unicode/#IsPrint. |
|
|
|
fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields, provided that the |
|
|
| If 'true', then the output is pretty printed. |
- HTTP method
-
POST - Description
- create rollback of a DeploymentConfig
| Parameter | Type | Description |
|---|---|---|
|
|
|
| HTTP code | Reponse body |
|---|---|
| 200 - OK |
|
| 201 - Created |
|
| 202 - Accepted |
|
| 401 - Unauthorized | Empty |
