Closed abuehrle closed 9 years ago
Should say that I probably need to add a reference for this example in here.
@kpoplin and @mjlodge I added a better value proposition to the intro of this guide. It's a newish guide for Kubernetes on CoreOS in Azure. It's based on an example that Kubernetes themselves wrote a few months ago. I have attempted to bring out the 'weave bits' and why weave is the only solution.
I like it @abuehrle - the only phrase I might tweak would be "Without Weave, implementing simple networking for your app across Kubernetes clusters can be involved."
When we had the discussion w/the Amazon folks on the ECS guide, I know they wanted to "soften up" the language about any AWS deficiencies, so probably the same here to be cautious of. But maybe "can be a complex [and/or time-consuming] process" -- ?
@kpoplin that's true. It's actually more a limitation of Docker than it is Kubernetes, so I will think about how to rephrase that.
It's based on an example that Kubernetes themselves wrote a few months ago.
I wrote it :)
I will need to remove all the scripts and leave just the readme, i.e. squash the history, as there are too many files in node_modules
that shouldn't be checked-in.
Also, we will need <link rel="canonical" href="...">
here, as the copy on the Kubernetes site should remain ranking well and our copy is just for convenience.
My apologies, @errordeveloper I did not know that! very good example.
On Oct 29, 2015, at 9:26 AM, Ilya Dmitrichenko notifications@github.com wrote:
It's based on an example that Kubernetes themselves wrote a few months ago.
I wrote it :)
— Reply to this email directly or view it on GitHub https://github.com/weaveworks/guides/pull/126#issuecomment-152214563.
We shouldn't have merged this in the current state, as it checks in 4k random files :(
Please remove the files that don’t belong —sorry about that. I can’t publish anything to the web anyway, as there are incomplete website changes sitting in staging at the moment.
On Nov 1, 2015, at 11:04 AM, Ilya Dmitrichenko notifications@github.com wrote:
We shouldn't have merged this in the current state, as it checks in 4k random files :(
— Reply to this email directly or view it on GitHub https://github.com/weaveworks/guides/pull/126#issuecomment-152844291.
@errordeveloper here is the initial cut of this file. Please read the intro section to see that I've pitched this correctly. I am working on the diagram now.
@pidster have a look when you get a chance. Anything we should include about weave and kubernetes here?