elasticsearch-operator
elasticsearch-operator copied to clipboard
upmc-enterprises
manages elasticsearch clusters
Currently, if you set a bad value for `zones` field in the CRD, the operator throws a bunch of errors and sometimes you need to kill the operator pod to...
* Deploy es daemonset in the same namespace of the crd * Delete daemonset object before a crd deletiong * Set history size in snapshots cronjob
Since operator makes Kubernete cluster private, no way I can access from outside. I understand port forward is a solution but it can't be permanent solution. That's why I have...
The Elasticsearch Operator should integrate with the Operator Lifecycle Manager, a component of the CoreOS Operator Framework (see https://github.com/operator-framework/operator-lifecycle-manager for details).
Cluster spec in processor have correct logic. Statefulset creation in k8sutil should not apply logic (the current one there is wrong because it defaults to non ssl)
Is there a known path to change the StorageClass without loosing the data? For instance, say we discover our workload needs more IOPS and we want to switch to a...
It would be cool to have an option to run client nodes without tls. There is software like graylog which does not like the self signed certs created by the...
``` time="2018-03-29T19:33:49Z" level=error msg="Error in init(): daemonsets.extensions \"elasticsearch-operator-sysctl\" already exists" ```
I was wondering how you would go about upgrading to a newer version of elasticsearch using this operator.
Currently backs up to S3, see if there's a way to accomplish the same.