"Kubernetes provides a first-class, native API object type in OpenShift Container Platform called Deployments. Deployments serve as a descendant of the OpenShift Container Platform-specific DeploymentConfig."

-
-
Replying to @caffeinepresent
Yeah, Deployments originated in OpenShift and were ported to upstream, from my understanding.
1 reply 0 retweets 0 likes -
Replying to @AlexB138
The story I heard (and this was back in 2016ish, secondhand and in passing, so take however many grains of salt), was:
1 reply 0 retweets 0 likes -
Replying to @caffeinepresent @AlexB138
When the community decided to rework replica management, DeploymentConfig managing ReplicationControllers was proposed by the folks from Red Hat, but the community eventually went with a different proposal of Deployment managing a new resource called a ReplicaSet.
1 reply 0 retweets 0 likes -
Replying to @caffeinepresent @AlexB138
The key issue seems to be kubernetes/kubernetes#1743, which almost five years later reads as
@smarterclayton proposing the adoption of DeploymentConfig as a result of existing discussion and@bgrant0607 taking off from there, paring it down and bending it into a different shape.1 reply 0 retweets 0 likes -
Replying to @caffeinepresent @AlexB138 and
The OpenShift doc text makes it sound like Kubernetes Deployment is a lineal descendant of OpenShift DeploymentConfig.
2 replies 1 retweet 1 like -
Deployment was inspired by DeploymentConfig, but I wanted to make updates continuous and the rollout constraints intent-oriented. Rather than the typical rate limit and max-in-flight, I proposed minReadySeconds and maxUnavailable. It was a big effort to get it to beta in 1.2
2 replies 0 retweets 7 likes -
To be fair, DC was taking most of our early discussions about what deployments *might* look like and then prototyping them. I do think more workload controllers would be better than fewer - it’s super hard to do that correctly still. We’re still finding bugs in replicasets.
1 reply 0 retweets 1 like
The learnings from Openshift were definitely valuable. Original upstream issue: http://issues.k8s.io/503 . And, yes, there are still known bugs in ReplicaSet, such ashttp://issues.k8s.io/22061
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.