I suppose we'll need to use "oc update -f $template" and track our
clusterquota templates (oc edit and oc patch aren't the nicest things to
idempotently automate). The nice thing about having --dry-run associated
is at least we wouldn't have to maintain YAML templates, and we could rely
on the API
All the basic CRUD commands work, so you can run `oc
edit clusterquota/name`, `oc patch clusterquota/name `, or `oc
update -f `.
On Tue, Nov 8, 2016 at 11:06 AM, Ben Pritchett wrote:
> Is there a method for updating clusterquotas that have already been
> created? Referencing the creation proces
Is there a method for updating clusterquotas that have already been
created? Referencing the creation process here:
https://docs.openshift.com/container-platform/3.3/admin_guide/multiproject_quota.html#multi-project-quotas-selecting-projects
There isn't a "oc update clusterquota foo" and the work
2016-11-08 16:43 GMT+01:00 Marko Lukša :
> Your version of oc is too old. Your file works for me, when I use 1.3.0+,
> but I get the same error as you when using 1.2.0.
>
Thanks !
I've created this issue: https://github.com/openshift/origin/issues/11836 «
Suggestion: append in `oc` a warning mes
Your version of oc is too old. Your file works for me, when I use
1.3.0+, but I get the same error as you when using 1.2.0.
On 08. 11. 2016 16:22, Stéphane Klein wrote:
> This error occurs when you specify multiple field references
simultaneously like fieldRef and resourceFieldRef together.
I
On Tue, Nov 8, 2016 at 10:22 AM, Stéphane Klein wrote:
> > This error occurs when you specify multiple field references
> simultaneously like fieldRef and resourceFieldRef together.
>
> I've only resourceFieldRef here:
>
> - name: MEMORY_LIMIT
> valueFrom:
> re
> This error occurs when you specify multiple field references
simultaneously like fieldRef and resourceFieldRef together.
I've only resourceFieldRef here:
- name: MEMORY_LIMIT
valueFrom:
resourceFieldRef:
resource: limits.memory
- nam
https://gist.github.com/harobed/fc24a7766dbcf2d9e61f42dd8a968a6c
2016-11-08 16:03 GMT+01:00 Avesh Agarwal :
>
>
> On Tue, Nov 8, 2016 at 8:50 AM, Stéphane Klein <
> cont...@stephane-klein.info> wrote:
>
>>
>>
>> 2016-11-08 13:43 GMT+01:00 Avesh Agarwal :
>>
>>>
>>>
>>> On Tue, Nov 8, 2016 at 5:44
On Tue, Nov 8, 2016 at 8:50 AM, Stéphane Klein
wrote:
>
>
> 2016-11-08 13:43 GMT+01:00 Avesh Agarwal :
>
>>
>>
>> On Tue, Nov 8, 2016 at 5:44 AM, Stéphane Klein <
>> cont...@stephane-klein.info> wrote:
>>
>>> Hi,
>>>
>>> I've this ReplicationController:
>>>
>>> apiVersion: v1
>>> kind: List
>>> m
Yes i did, but i don't let ansible touch it since we started without the
metrics playbooks and it's hard to reintroduce.
At my case, Registry, Routers, Metrics and Logging are managed a part from
playbooks.
---
Diego Castro / The CloudFather
GetupCloud.com - Eliminamos a Gravidade
2016-11-08 10
2016-11-08 13:43 GMT+01:00 Avesh Agarwal :
>
>
> On Tue, Nov 8, 2016 at 5:44 AM, Stéphane Klein <
> cont...@stephane-klein.info> wrote:
>
>> Hi,
>>
>> I've this ReplicationController:
>>
>> apiVersion: v1
>> kind: List
>> metadata: {}
>> items:
>> - apiVersion: v1
>> kind: ReplicationController
On Mon, Nov 7, 2016 at 5:31 PM, Diego Castro
wrote:
> Hi Philippe i have upgraded without major issues using blue/green upgrade.
> The only thing was the secured registry that i managed to solve turning off
> the hosted registry at inventory file.
>
Thanks for sharing this. Do you use metrics in
On Tue, Nov 8, 2016 at 5:44 AM, Stéphane Klein
wrote:
> Hi,
>
> I've this ReplicationController:
>
> apiVersion: v1
> kind: List
> metadata: {}
> items:
> - apiVersion: v1
> kind: ReplicationController
> metadata:
> labels:
> metrics-infra: hawkular-cassandra
> name: hawkular-
Same error here:
http://lists.openshift.redhat.com/openshift-archives/users/2016-October/msg00082.html
2016-11-08 12:00 GMT+01:00 Stéphane Klein :
> With resourceFieldRef like here https://github.com/openshift/
> origin-metrics/blob/master/deployer/templates/hawkular-
> cassandra-node-emptydir.ya
With resourceFieldRef like here
https://github.com/openshift/origin-metrics/blob/master/deployer/templates/hawkular-cassandra-node-emptydir.yaml#L83
I have this error:
Error from server: ReplicationController "hawkular-cassandra-1" is invalid:
[spec.template.spec.containers[0].env[5].valueFrom: I
Hi,
I've this ReplicationController:
apiVersion: v1
kind: List
metadata: {}
items:
- apiVersion: v1
kind: ReplicationController
metadata:
labels:
metrics-infra: hawkular-cassandra
name: hawkular-cassandra
type: hawkular-cassandra
name: hawkular-cassandra-1
spec:
16 matches
Mail list logo
