Skip to content

The literal kind is "DeploymentConfig" not "DeploymentConfiguration" #7842

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 2, 2018
Merged

The literal kind is "DeploymentConfig" not "DeploymentConfiguration" #7842

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions architecture/core_concepts/deployments.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ deployments also provide the ability to transition from an existing
deployment of an image to a new one and also define hooks to be run
before or after creating the replication controller.

The {product-title} `*DeploymentConfiguration*` object defines the following
The {product-title} `*DeploymentConfig*` object defines the following
details of a deployment:

1. The elements of a `*ReplicationController*` definition.
Expand All @@ -145,7 +145,7 @@ controller is retained to enable easy rollback if needed.
For detailed instructions on how to create and interact with deployments,
refer to xref:../../dev_guide/deployments/basic_deployment_operations.adoc#dev-guide-basic-deployment-operations[Deployments].

Here is an example `*DeploymentConfiguration*` definition with some
Here is an example `*DeploymentConfig*` definition with some
omissions and callouts:

[source,yaml]
Expand Down