Re: Kubernetes cloud provider

2018-09-07 Thread Rohit Yadav
Let me engage on the PR, apart from what Wei has shared we may also need to
add some additional support/features in future.

- Rohit

On Thu, Sep 6, 2018 at 12:50 PM, Wei ZHOU  wrote:

> Hi Sebastien,
>
> We (as Leaseweb) are using CloudStack plugin in our kubernetes clusters
> [1][2].
> The main usage are
> (1) CloudStack will acquire a public IP and create LB rules when we create
> a LoadBalancer service in kubernetes
> (2) CloudStack will create/remove load balancer rules when we scale out/in
> a cluster.
>
> If the plugin is removed from kubernetes because nobody works on making it
> external, we have to maintain IP and LB rules manually.
>
>
> [1]https://kubernetes.io/docs/tasks/access-application-
> cluster/create-external-load-balancer/
> [2]https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider/
> providers/cloudstack
>
> Kind regards,
> Wei Zhou
>
> Sebastien Goasguen  于2018年9月4日周二 上午8:18写道:
>
>> Hi all, it has been a while.
>>
>> Please see this:
>>
>> https://github.com/kubernetes/kubernetes/pull/68199
>>
>> I don't know if anyone is using it but if we don't reply the cloudstack
>> controller in kubernetes might get removed from the upstream.
>>
>> -seb
>>
>


Re: Kubernetes cloud provider

2018-09-07 Thread Sebastien Goasguen
Right,

So you need to engage in this PR:
https://github.com/kubernetes/kubernetes/pull/68199

or send me email seb...@cloudtank.ch


On Thu, Sep 6, 2018 at 9:20 AM Wei ZHOU  wrote:

> Hi Sebastien,
>
> We (as Leaseweb) are using CloudStack plugin in our kubernetes clusters
> [1][2].
> The main usage are
> (1) CloudStack will acquire a public IP and create LB rules when we create
> a LoadBalancer service in kubernetes
> (2) CloudStack will create/remove load balancer rules when we scale out/in
> a cluster.
>
> If the plugin is removed from kubernetes because nobody works on making it
> external, we have to maintain IP and LB rules manually.
>
>
> [1]
> https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/
> [2]
> https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider/providers/cloudstack
>
> Kind regards,
> Wei Zhou
>
> Sebastien Goasguen  于2018年9月4日周二 上午8:18写道:
>
>> Hi all, it has been a while.
>>
>> Please see this:
>>
>> https://github.com/kubernetes/kubernetes/pull/68199
>>
>> I don't know if anyone is using it but if we don't reply the cloudstack
>> controller in kubernetes might get removed from the upstream.
>>
>> -seb
>>
>


Re: Kubernetes cloud provider

2018-09-06 Thread Wei ZHOU
Hi Sebastien,

We (as Leaseweb) are using CloudStack plugin in our kubernetes clusters
[1][2].
The main usage are
(1) CloudStack will acquire a public IP and create LB rules when we create
a LoadBalancer service in kubernetes
(2) CloudStack will create/remove load balancer rules when we scale out/in
a cluster.

If the plugin is removed from kubernetes because nobody works on making it
external, we have to maintain IP and LB rules manually.


[1]
https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/
[2]
https://github.com/kubernetes/kubernetes/tree/master/pkg/cloudprovider/providers/cloudstack

Kind regards,
Wei Zhou

Sebastien Goasguen  于2018年9月4日周二 上午8:18写道:

> Hi all, it has been a while.
>
> Please see this:
>
> https://github.com/kubernetes/kubernetes/pull/68199
>
> I don't know if anyone is using it but if we don't reply the cloudstack
> controller in kubernetes might get removed from the upstream.
>
> -seb
>


Re: Kubernetes cloud provider

2018-09-05 Thread Will Stevens
That is part of it. The bigger issue is, who is maintaining that code?

On Wed, Sep 5, 2018, 6:10 AM Rafael Weingärtner 
wrote:

> So, it is a matter of getting the code from one repository and sending to
> other under Kubernetes org in Github?
>
> On Wed, Sep 5, 2018 at 5:20 AM, Sebastien Goasguen 
> wrote:
>
> > On Tue, Sep 4, 2018 at 11:28 PM Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> > > Hi Sebastian,
> > >
> > > I read the thread there, but I did not understand it. What do they need
> > > from us?
> > > We should work with to maintain this integration.
> > >
> > >
> > They are going to remove it from the core kubernetes code base. Ideally
> it
> > should go in another repo in the kubernetes github org like
> > https://github.com/kubernetes/cloud-provider-openstack
> >
> > If nobody pick this up and gets involved, the provider will just
> disappear.
> >
> > You could also put it in github.com/cloudstack-extras or something out
> of
> > the kubernetes maintained code base
> >
> >
> >
> > > On Tue, Sep 4, 2018 at 3:18 AM, Sebastien Goasguen 
> > > wrote:
> > >
> > >> Hi all, it has been a while.
> > >>
> > >> Please see this:
> > >>
> > >> https://github.com/kubernetes/kubernetes/pull/68199
> > >>
> > >> I don't know if anyone is using it but if we don't reply the
> cloudstack
> > >> controller in kubernetes might get removed from the upstream.
> > >>
> > >> -seb
> > >>
> > >
> > >
> > >
> > > --
> > > Rafael Weingärtner
> > >
> >
>
>
>
> --
> Rafael Weingärtner
>


Re: Kubernetes cloud provider

2018-09-05 Thread Rafael Weingärtner
So, it is a matter of getting the code from one repository and sending to
other under Kubernetes org in Github?

On Wed, Sep 5, 2018 at 5:20 AM, Sebastien Goasguen  wrote:

> On Tue, Sep 4, 2018 at 11:28 PM Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Hi Sebastian,
> >
> > I read the thread there, but I did not understand it. What do they need
> > from us?
> > We should work with to maintain this integration.
> >
> >
> They are going to remove it from the core kubernetes code base. Ideally it
> should go in another repo in the kubernetes github org like
> https://github.com/kubernetes/cloud-provider-openstack
>
> If nobody pick this up and gets involved, the provider will just disappear.
>
> You could also put it in github.com/cloudstack-extras or something out of
> the kubernetes maintained code base
>
>
>
> > On Tue, Sep 4, 2018 at 3:18 AM, Sebastien Goasguen 
> > wrote:
> >
> >> Hi all, it has been a while.
> >>
> >> Please see this:
> >>
> >> https://github.com/kubernetes/kubernetes/pull/68199
> >>
> >> I don't know if anyone is using it but if we don't reply the cloudstack
> >> controller in kubernetes might get removed from the upstream.
> >>
> >> -seb
> >>
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>



-- 
Rafael Weingärtner


Re: Kubernetes cloud provider

2018-09-05 Thread Sebastien Goasguen
On Tue, Sep 4, 2018 at 11:28 PM Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Hi Sebastian,
>
> I read the thread there, but I did not understand it. What do they need
> from us?
> We should work with to maintain this integration.
>
>
They are going to remove it from the core kubernetes code base. Ideally it
should go in another repo in the kubernetes github org like
https://github.com/kubernetes/cloud-provider-openstack

If nobody pick this up and gets involved, the provider will just disappear.

You could also put it in github.com/cloudstack-extras or something out of
the kubernetes maintained code base



> On Tue, Sep 4, 2018 at 3:18 AM, Sebastien Goasguen 
> wrote:
>
>> Hi all, it has been a while.
>>
>> Please see this:
>>
>> https://github.com/kubernetes/kubernetes/pull/68199
>>
>> I don't know if anyone is using it but if we don't reply the cloudstack
>> controller in kubernetes might get removed from the upstream.
>>
>> -seb
>>
>
>
>
> --
> Rafael Weingärtner
>


Re: Kubernetes cloud provider

2018-09-04 Thread Rafael Weingärtner
Hi Sebastian,

I read the thread there, but I did not understand it. What do they need
from us?
We should work with to maintain this integration.

On Tue, Sep 4, 2018 at 3:18 AM, Sebastien Goasguen  wrote:

> Hi all, it has been a while.
>
> Please see this:
>
> https://github.com/kubernetes/kubernetes/pull/68199
>
> I don't know if anyone is using it but if we don't reply the cloudstack
> controller in kubernetes might get removed from the upstream.
>
> -seb
>



-- 
Rafael Weingärtner


Kubernetes cloud provider

2018-09-04 Thread Sebastien Goasguen
Hi all, it has been a while.

Please see this:

https://github.com/kubernetes/kubernetes/pull/68199

I don't know if anyone is using it but if we don't reply the cloudstack
controller in kubernetes might get removed from the upstream.

-seb