Re: Excluding replacement pods from quota?

2016-05-02 Thread Clayton Coleman
Or set maxUnavailable to 100% in your rolling deployment config.

On Mon, May 2, 2016 at 10:59 AM, Luke Meyer  wrote:
> Use the Recreate deploy strategy rather than Rolling.
> https://docs.openshift.org/latest/dev_guide/deployments.html#recreate-strategy
>
> On Sat, Apr 30, 2016 at 10:24 PM, Andrew Lau  wrote:
>>
>> Hi,
>>
>> Is there a way to have the old pod moved into the terminating scope? Or is
>> there an alternative solution for the following use case:
>>
>> User has the following quota:
>> 1 pod in terminating scope
>> 1 pod in non-terminating scope
>>
>> For new builds, the build will complete in the terminating scope but the
>> replacement pod will not be able to start due to the quota.
>>
>> ___
>> dev mailing list
>> dev@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>
>
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>

___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev


Re: Excluding replacement pods from quota?

2016-05-02 Thread Luke Meyer
Use the Recreate deploy strategy rather than Rolling.
https://docs.openshift.org/latest/dev_guide/deployments.html#recreate-strategy

On Sat, Apr 30, 2016 at 10:24 PM, Andrew Lau  wrote:

> Hi,
>
> Is there a way to have the old pod moved into the terminating scope? Or is
> there an alternative solution for the following use case:
>
> User has the following quota:
> 1 pod in terminating scope
> 1 pod in non-terminating scope
>
> For new builds, the build will complete in the terminating scope but the
> replacement pod will not be able to start due to the quota.
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev


Excluding replacement pods from quota?

2016-04-30 Thread Andrew Lau
Hi,

Is there a way to have the old pod moved into the terminating scope? Or is
there an alternative solution for the following use case:

User has the following quota:
1 pod in terminating scope
1 pod in non-terminating scope

For new builds, the build will complete in the terminating scope but the
replacement pod will not be able to start due to the quota.
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev