Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Use "requests" for CPU resources instead of limits | Peter Portante | 2017-10-19 | 1 | -1/+14 |
| | | | | | | | | | | | | | | | We now use a CPU request to ensure logging infrastructure pods are not capped by default for CPU usage. It is still important to ensure we have a minimum amount of CPU. We keep the use of the variables *_cpu_limit so that the existing behavior is maintained. Note that we don't want to cap an infra pod's CPU usage by default, since we want to be able to use the necessary resources to complete it's tasks. Bug 1501960 (https://bugzilla.redhat.com/show_bug.cgi?id=1501960) | ||||
* | logging set memory request to limit | Jeff Cantrill | 2017-08-30 | 1 | -0/+2 |
| | |||||
* | Revert "logging set memory request to limit" | Scott Dodson | 2017-08-29 | 1 | -2/+0 |
| | |||||
* | logging set memory request to limit | Jeff Cantrill | 2017-08-23 | 1 | -0/+2 |
| | |||||
* | Updating template parameter replica to be more unique to avoid var scope ↵ | ewolinetz | 2017-07-27 | 1 | -1/+1 |
| | | | | creeping | ||||
* | fix curator host, port params; remove curator es volumes | Rich Megginson | 2017-05-31 | 1 | -5/+0 |
| | |||||
* | Create logging deployments with non-zero replica counts | Steve Kuznetsov | 2017-05-22 | 1 | -1/+1 |
| | | | | | | | | | | | | When we currently create the set of logging `DeploymentConfig`s, we create them with zero desired replicas. This causes the deployment to immediately succeed as there is no work to be done. This inhibits our ability to use nice CLI UX features like `oc rollout status` to monitor the logging stack deployments. Instead, we should can create the configs with the correct number of replicas in the first place and stop using `oc scale` to bring them up after the fact. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com> | ||||
* | Decomposing openshift_logging role into subcomponent roles | ewolinetz | 2017-05-22 | 1 | -0/+103 |