Re: [kubernetes-users] Multiple version of software on same namespace

2017-10-31 Thread Rui Goncalves 
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
> 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 instances of the same application.  You
> can "helm install" many copies, with each one getting unique labels that
> can be used by your service label selectors.
>
>
>
>
>
> On Tuesday, October 31, 2017 at 8:08:54 AM UTC-6, rgonc...@gmail.com
> wrote:
>>
>> On Tuesday, October 31, 2017 at 7:41:45 AM UTC, Rodrigo Campos wrote:
>> > On Mon, Oct 30, 2017 at 03:34:00AM -0700, rgonc...@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 just to separate
>> slightly different resources, such as different versions of the same
>> software: use labels to distinguish resources within the same namespace."
>> > >
>> > > The only way (that I know of) to separate multiple versions of same
>> software on the same namespace is naming services in accordance to software
>> version, adjust the selector field and tag pods appropriately. This has
>> maintenance overhead and I'm required to reference services with a
>> different name according to the desired version. I don't think this is a
>> solution.
>> >
>> > Why not? What is the problem you want to solve?
>> >
>> > >
>> > > I don't see any other way besides using namespaces. What am I missing
>> something?
>> >
>> > I think services is the way to do it, with labels on deplyoments, but I
>> might be
>> > missing the details of what you want to do. Can you pelase elaborate?
>>
>> Basically I want to be able to deploy two distinct versions of the same
>> software on the same kubernetes cluster. This is a cluster used for
>> development and it's usual to have multiple versions of the same software
>> (ex. maintenance version and evolution version).
>>
>> I can create one namespace for each version, but I'd rather not because
>> I'd like to limit resource usage per software, not per software version.
>> But without using namespaces, the only way (like I said, that I'm aware
>> of), is to codify the version of the service on the name (serviceA-v1.1;
>> serviceA-trunk; etc...). Definitely I don't want to do that. Doing that
>> implies changing kubernetes deployment descriptors, clients must change the
>> service they reference, etc... not a good idea.
>>
>> I'm asking because the statement on the docs saying the using namespaces
>> it's not necessary to separate multiple versions of the same software.
>> However I think it is.
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Kubernetes user discussion and Q" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/kubernetes-users/_zeW8m9ZX9g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] Multiple version of software on same namespace

2017-10-31 Thread Warren Strange 

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 instances of the same application.  You 
can "helm install" many copies, with each one getting unique labels that 
can be used by your service label selectors.

 



On Tuesday, October 31, 2017 at 8:08:54 AM UTC-6, rgonc...@gmail.com wrote:
>
> On Tuesday, October 31, 2017 at 7:41:45 AM UTC, Rodrigo Campos wrote:
> > On Mon, Oct 30, 2017 at 03:34:00AM -0700, rgonc...@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 just to separate 
> slightly different resources, such as different versions of the same 
> software: use labels to distinguish resources within the same namespace."
> > > 
> > > The only way (that I know of) to separate multiple versions of same 
> software on the same namespace is naming services in accordance to software 
> version, adjust the selector field and tag pods appropriately. This has 
> maintenance overhead and I'm required to reference services with a 
> different name according to the desired version. I don't think this is a 
> solution.
> > 
> > Why not? What is the problem you want to solve?
> > 
> > > 
> > > I don't see any other way besides using namespaces. What am I missing 
> something?
> > 
> > I think services is the way to do it, with labels on deplyoments, but I 
> might be
> > missing the details of what you want to do. Can you pelase elaborate?
>
> Basically I want to be able to deploy two distinct versions of the same 
> software on the same kubernetes cluster. This is a cluster used for 
> development and it's usual to have multiple versions of the same software 
> (ex. maintenance version and evolution version).
>
> I can create one namespace for each version, but I'd rather not because 
> I'd like to limit resource usage per software, not per software version. 
> But without using namespaces, the only way (like I said, that I'm aware 
> of), is to codify the version of the service on the name (serviceA-v1.1; 
> serviceA-trunk; etc...). Definitely I don't want to do that. Doing that 
> implies changing kubernetes deployment descriptors, clients must change the 
> service they reference, etc... not a good idea.
>
> I'm asking because the statement on the docs saying the using namespaces 
> it's not necessary to separate multiple versions of the same software. 
> However I think it is.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] Multiple version of software on same namespace

2017-10-31 Thread rgoncalves 
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. 
> > According to the docs: 
> > 
> > "It is not necessary to use multiple namespaces just to separate slightly 
> > different resources, such as different versions of the same software: use 
> > labels to distinguish resources within the same namespace."
> > 
> > The only way (that I know of) to separate multiple versions of same 
> > software on the same namespace is naming services in accordance to software 
> > version, adjust the selector field and tag pods appropriately. This has 
> > maintenance overhead and I'm required to reference services with a 
> > different name according to the desired version. I don't think this is a 
> > solution.
> 
> Why not? What is the problem you want to solve?
> 
> > 
> > I don't see any other way besides using namespaces. What am I missing 
> > something?
> 
> I think services is the way to do it, with labels on deplyoments, but I might 
> be
> missing the details of what you want to do. Can you pelase elaborate?

Basically I want to be able to deploy two distinct versions of the same 
software on the same kubernetes cluster. This is a cluster used for development 
and it's usual to have multiple versions of the same software (ex. maintenance 
version and evolution version).

I can create one namespace for each version, but I'd rather not because I'd 
like to limit resource usage per software, not per software version. But 
without using namespaces, the only way (like I said, that I'm aware of), is to 
codify the version of the service on the name (serviceA-v1.1; serviceA-trunk; 
etc...). Definitely I don't want to do that. Doing that implies changing 
kubernetes deployment descriptors, clients must change the service they 
reference, etc... not a good idea.

I'm asking because the statement on the docs saying the using namespaces it's 
not necessary to separate multiple versions of the same software. However I 
think it is.


-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] Multiple version of software on same namespace

2017-10-31 Thread rgoncalves 
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 the same product has at least two 
development branches. A maintenance branch (ex. 1.3.x) and a trunk version (ex. 
2.0). 

So, it's not a switchover. The two version will coexist.

> 
> 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 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 the same software: use 
> > labels to distinguish resources within the same namespace."
> >
> > The only way (that I know of) to separate multiple versions of same 
> > software on the same namespace is naming services in accordance to software 
> > version, adjust the selector field and tag pods appropriately. This has 
> > maintenance overhead and I'm required to reference services with a 
> > different name according to the desired version. I don't think this is a 
> > solution.
> >
> > I don't see any other way besides using namespaces. What am I missing 
> > something?
> >
> > Thanks for any help.
> >
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Kubernetes user discussion and Q" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to kubernetes-users+unsubscr...@googlegroups.com.
> > To post to this group, send email to kubernetes-users@googlegroups.com.
> > Visit this group at https://groups.google.com/group/kubernetes-users.
> > For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] Multiple version of software on same namespace

2017-10-31 Thread Rodrigo Campos 
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 just to separate slightly 
> different resources, such as different versions of the same software: use 
> labels to distinguish resources within the same namespace."
> 
> The only way (that I know of) to separate multiple versions of same software 
> on the same namespace is naming services in accordance to software version, 
> adjust the selector field and tag pods appropriately. This has maintenance 
> overhead and I'm required to reference services with a different name 
> according to the desired version. I don't think this is a solution.

Why not? What is the problem you want to solve?

> 
> I don't see any other way besides using namespaces. What am I missing 
> something?

I think services is the way to do it, with labels on deplyoments, but I might be
missing the details of what you want to do. Can you pelase elaborate?

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Re: [kubernetes-users] Multiple version of software on same namespace

2017-10-30 Thread 'Tim Hockin' via Kubernetes user discussion and Q 
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 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 the same software: use 
> labels to distinguish resources within the same namespace."
>
> The only way (that I know of) to separate multiple versions of same software 
> on the same namespace is naming services in accordance to software version, 
> adjust the selector field and tag pods appropriately. This has maintenance 
> overhead and I'm required to reference services with a different name 
> according to the desired version. I don't think this is a solution.
>
> I don't see any other way besides using namespaces. What am I missing 
> something?
>
> Thanks for any help.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Kubernetes user discussion and Q" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

[kubernetes-users] Multiple version of software on same namespace

2017-10-30 Thread rgoncalves 
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 the same software: use 
labels to distinguish resources within the same namespace."

The only way (that I know of) to separate multiple versions of same software on 
the same namespace is naming services in accordance to software version, adjust 
the selector field and tag pods appropriately. This has maintenance overhead 
and I'm required to reference services with a different name according to the 
desired version. I don't think this is a solution.

I don't see any other way besides using namespaces. What am I missing something?

Thanks for any help.

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.