Thanks Warren. Really helpful.
I'll tale a look at helm.
On Tue, Oct 31, 2017 at 2:50 PM, Warren Strange
wrote:
>
> What you are describing is a really good use case for namespaces.
>
> If you really want to deploy multiple instances to the same namespace, you
>
What you are describing is a really good use case for namespaces.
If you really want to deploy multiple instances to the same namespace, you
could have a look at how some of the Helm charts do this.
Some charts use dynamic labels to (e.g. app={{ .Release.Name }} ) to
distinguish multiple
On Tuesday, October 31, 2017 at 7:41:45 AM UTC, Rodrigo Campos wrote:
> On Mon, Oct 30, 2017 at 03:34:00AM -0700, rgoncal...@gmail.com wrote:
> > I'm trying to figure out what's the best approach to deploy multiple
> > versions of the same software in kubernetes without relying on namespaces.
>
On Monday, October 30, 2017 at 3:31:01 PM UTC, Tim Hockin wrote:
> What are you trying to do? Do you want 2 versions in perpetuity or do
> you want to do some form of switchover?
I'm trying to figure out the best approach to create an application deployment
environment using Kubernetes. Usually
On Mon, Oct 30, 2017 at 03:34:00AM -0700, rgoncal...@gmail.com wrote:
> I'm trying to figure out what's the best approach to deploy multiple versions
> of the same software in kubernetes without relying on namespaces. According
> to the docs:
>
> "It is not necessary to use multiple namespaces
What are you trying to do? Do you want 2 versions in perpetuity or do
you want to do some form of switchover?
On Mon, Oct 30, 2017 at 3:34 AM, wrote:
> I'm trying to figure out what's the best approach to deploy multiple versions
> of the same software in kubernetes
I'm trying to figure out what's the best approach to deploy multiple versions
of the same software in kubernetes without relying on namespaces. According to
the docs:
"It is not necessary to use multiple namespaces just to separate slightly
different resources, such as different versions of