DeploymentConfigs deprecation in API reference docs

martin-aders · Jun 10, 2023 · fa07e3a · fa07e3a
1 parent ca79cab
commit fa07e3a
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 3 deletions.
diff --git a/apps/v1/generated.proto b/apps/v1/generated.proto
diff --git a/apps/v1/types.go b/apps/v1/types.go
@@ -29,6 +29,7 @@ import (
 // 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.
 // +openshift:compatibility-gen:level=1
 type DeploymentConfig struct {
 	metav1.TypeMeta `json:",inline"`

diff --git a/apps/v1/zz_generated.swagger_doc_generated.go b/apps/v1/zz_generated.swagger_doc_generated.go
diff --git a/openapi/generated_openapi/zz_generated.openapi.go b/openapi/generated_openapi/zz_generated.openapi.go
diff --git a/openapi/openapi.json b/openapi/openapi.json
@@ -328,7 +328,7 @@
       }
     },
     "com.github.openshift.api.apps.v1.DeploymentConfig": {
-      "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.\n\nA 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.\n\nCompatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).",
+      "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.\n\nA 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.\n\nCompatibility 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"