From 5b30477a0ff0ea57de60162926a43e7cfe48a16c Mon Sep 17 00:00:00 2001 From: AdamDang Date: Sun, 6 May 2018 23:31:23 +0800 Subject: [PATCH 1/2] Typo fix: Kuberntes->Kubernetes Kuberntes->Kubernetes --- contributors/design-proposals/storage/grow-volume-size.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/design-proposals/storage/grow-volume-size.md b/contributors/design-proposals/storage/grow-volume-size.md index 4fb53292f..a968d91c6 100644 --- a/contributors/design-proposals/storage/grow-volume-size.md +++ b/contributors/design-proposals/storage/grow-volume-size.md @@ -198,7 +198,7 @@ we have considered following options: Cons: * I don't know if there is a pattern that exists in kube today for shipping shell scripts that are called out from code in Kubernetes. Flex is - different because, none of the flex scripts are shipped with Kuberntes. + different because, none of the flex scripts are shipped with Kubernetes. 3. Ship resizing tools in a container. From e2a23c323c52c9ed37089bf4d651f1ec4f6f26e4 Mon Sep 17 00:00:00 2001 From: AdamDang Date: Sun, 6 May 2018 23:33:48 +0800 Subject: [PATCH 2/2] Update application_service_definition_notes.md --- .../application_service_definition_notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/events/2016/developer-summit-2016/application_service_definition_notes.md b/events/2016/developer-summit-2016/application_service_definition_notes.md index e8f4c0c54..8cf3bb9dd 100644 --- a/events/2016/developer-summit-2016/application_service_definition_notes.md +++ b/events/2016/developer-summit-2016/application_service_definition_notes.md @@ -16,7 +16,7 @@ We need the 80% case, Fabric8 is a good example of this. We need a good set of We also need to look at how to get developer feedback on this so that we're building what they need. Pradeepto did a comparison of Kompose vs. Docker Compose for simplicity/usability. -One of the things we're discussing the Kompose API. We want to get rid of this and supply something which people can use directly with kuberntes. A bunch of shops only have developers. Someone asked though what's so complicated with Kube definitions. Have we identified what gives people trouble with this? We push too many concepts on developers too quickly. We want some high-level abstract types which represent the 95% use case. Then we could decompose these to the real types. +One of the things we're discussing the Kompose API. We want to get rid of this and supply something which people can use directly with kubernetes. A bunch of shops only have developers. Someone asked though what's so complicated with Kube definitions. Have we identified what gives people trouble with this? We push too many concepts on developers too quickly. We want some high-level abstract types which represent the 95% use case. Then we could decompose these to the real types. What's the gap between compose files and the goal? As an example, say you want to run a webserver pod. You have to deal with ingress, and service, and replication controller, and a bunch of other things. What's the equivalent of "docker run" which is easy to get. The critical thing is how fast you can learn it.