csa/devops/ansible-patches/openshift.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	logging set memory request to limit	Jeff Cantrill	2017-08-23	1	-0/+4
\|
*	Fix syntax for when statement	Rodolfo Carvalho	2017-08-10	1	-3/+3
\| \| \| \| \| \| \| \|	Without that, playbook runs print warnings such as this: [WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: {{ g_etcd_hosts is not defined and g_new_etcd_hosts is not defined}}
*	Updating template parameter replica to be more unique to avoid var scope ↵	ewolinetz	2017-07-27	2	-2/+2
\| \| \| \|	creeping
*	Updating openshift_logging_kibana default for kibana hostname	ewolinetz	2017-07-21	1	-1/+1
\|
*	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	2	-18/+44
\| \| \| \|	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
\|
*	Add a readiness probe to the Kibana container	Steve Kuznetsov	2017-05-22	1	-0/+7
\| \| \| \| \| \| \| \| \|	In order to ensure that the Kubernetes machinery can determine when the Kibana Pods are becoming ready, we need to add a readiness probe to the Containers that make up those pods. The Kibana readiness probe simply hits the base URL at `http://localhost:5601/` and expects a 200. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
*	Create logging deployments with non-zero replica counts	Steve Kuznetsov	2017-05-22	2	-10/+2
\| \| \| \| \| \| \| \| \| \| \| \|	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 changes from master branch	ewolinetz	2017-05-22	2	-2/+29
\|
*	Pulling in changes from master	ewolinetz	2017-05-22	1	-2/+20
\|
*	Decomposing openshift_logging role into subcomponent roles	ewolinetz	2017-05-22	8	-0/+464