You can create a secret with a file that has content like:
.defaults:
delete:
days: 7
runhour: 0
runminute: 0
and add the volume to the deployment config as described here:
https://github.com/openshift/origin-aggregated-logging/tree/v1.2.0#curator
Alternatively, if you do not provide the secret, you could update the
following value in the deploymentconfig:
https://github.com/openshift/origin-aggregated-logging/blob/v1.2.0/deployment/templates/curator.yaml#L90
https://github.com/openshift/origin-aggregated-logging/tree/v1.2.0
On Tue, Nov 22, 2016 at 9:34 AM, Den Cowboy <[email protected]> wrote:
> Hi,
>
>
> We have an origin 1.2.0 cluster in which we've integrated the logging
> project. It works fine but we just followed the setup tutorial. We don't
> know may about the real setup.
>
>
> We're facing sometimes issues that our disk is getting too fill because
> our ES is keeping to many data.
>
> How can we easily configure the curator to delete every log of every
> project once a week?
>
>
> We took a look to the documentation:
>
> myapp-dev:
> delete:
> days: 1
>
> myapp-qe:
> delete:
> weeks: 1
>
> .operations:
> delete:
> weeks: 8
>
> .defaults:
> delete:
> days: 30
> runhour: 0
> runminute: 0
>
> But it isn't clear for us. Isn't there just a setting in the
> deploymentconfig or what's the most easy approach for this?
>
>
> Thanks
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
--
--
Jeff Cantrill
Senior Software Engineer, Red Hat Engineering
OpenShift Integration Services
Red Hat, Inc.
*Office*: 703-748-4420 | 866-546-8970 ext. 8162420
[email protected]
http://www.redhat.com
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
