Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Adding labels for elasticsearch and kibana services | ewolinetz | 2017-06-29 | 1 | -3/+2 |
| | |||||
* | Updated to using oo_random_word for secret gen | ewolinetz | 2017-06-08 | 1 | -2/+2 |
| | |||||
* | Updating kibana to store session and oauth secrets for reuse, fix ↵ | ewolinetz | 2017-06-08 | 1 | -16/+40 |
| | | | | oauthclient generation for ops | ||||
* | Updating Kibana-proxy secret key name, fixing deleting secrets, fixed extra ↵ | ewolinetz | 2017-05-31 | 1 | -2/+2 |
| | | | | ES dc creation | ||||
* | Fixing tux warnings and some final clean up | ewolinetz | 2017-05-23 | 1 | -11/+11 |
| | |||||
* | Appease travis | Scott Dodson | 2017-05-22 | 1 | -4/+4 |
| | |||||
* | Create logging deployments with non-zero replica counts | Steve Kuznetsov | 2017-05-22 | 1 | -9/+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> | ||||
* | Pulling in changes from master | ewolinetz | 2017-05-22 | 1 | -2/+20 |
| | |||||
* | Decomposing openshift_logging role into subcomponent roles | ewolinetz | 2017-05-22 | 1 | -0/+222 |