elasticsearch 使用Elasticsearch和Kibana的集群级日志记录在kubernetes中不起作用

我正在尝试按照下面的链接设置群集日志记录

my config-default.sh

# Optional: Enable node logging.
ENABLE_NODE_LOGGING=**true**

LOGGING_DESTINATION=${LOGGING_DESTINATION:-**elasticsearch**}

# Optional: When set to true, Elasticsearch and Kibana will be setup as part of the cluster bring up.
ENABLE_CLUSTER_LOGGING=true

ELASTICSEARCH_LOGGING_REPLICAS=${ELASTICSEARCH_LOGGING_REPLICAS:-1}

命令

$ sudo kubectl get pods --namespace=kube-system

NAME                READY     STATUS    RESTARTS   AGE

kube-dns-v9-epplg   4/4       Running   0          20h

kube-ui-v3-i4von    1/1       Running   0          18h

---

正如您所看到的，我启用了日志记录，并将日志记录目标设置为elasticsearch。我没有看到elasticsearch日志或fluentd elasticsearch或kibana日志，当我得到豆荚时。似乎没有创建复制控制器、服务或POD，我还需要做些什么来启动ElasticSearch和Kibana吗？

您的集群从哪里开始？我试图在GCE上使用1.0.7版本和从HEAD复制这个，但没有成功

使用1.0.7版本：

$ kubectl get pods --namespace=kube-system
NAME                                           READY     STATUS    RESTARTS   AGE
elasticsearch-logging-v1-6x82b                 1/1       Running   0          3m
elasticsearch-logging-v1-s4bj5                 1/1       Running   0          3m
fluentd-elasticsearch-kubernetes-minion-ijpr   1/1       Running   0          1m
fluentd-elasticsearch-kubernetes-minion-nrya   1/1       Running   0          2m
fluentd-elasticsearch-kubernetes-minion-ppls   1/1       Running   0          1m
fluentd-elasticsearch-kubernetes-minion-sy4x   1/1       Running   0          2m
kibana-logging-v1-6qka9                        1/1       Running   0          3m
kube-dns-v8-9hyzm                              4/4       Running   0          3m
kube-ui-v1-11r3b                               1/1       Running   0          3m
monitoring-heapster-v6-4uzam                   1/1       Running   1          3m
monitoring-influx-grafana-v1-euc3a             2/2       Running   0          3m

摘自head：

$ kubectl get pods --namespace=kube-system
NAME                                           READY     STATUS    RESTARTS   AGE
elasticsearch-logging-v1-9gqs8                 1/1       Running   0          3m
elasticsearch-logging-v1-edb97                 1/1       Running   0          3m
etcd-server-events-kubernetes-master           1/1       Running   0          3m
etcd-server-kubernetes-master                  1/1       Running   0          3m
fluentd-elasticsearch-kubernetes-master        1/1       Running   0          2m
fluentd-elasticsearch-kubernetes-minion-6id6   1/1       Running   0          1m
fluentd-elasticsearch-kubernetes-minion-n25a   1/1       Running   0          1m
fluentd-elasticsearch-kubernetes-minion-x4wa   1/1       Running   0          1m
heapster-v10-ek03n                             1/1       Running   0          3m
kibana-logging-v1-ybsad                        1/1       Running   0          3m
kube-apiserver-kubernetes-master               1/1       Running   0          3m
kube-controller-manager-kubernetes-master      1/1       Running   0          3m
kube-dns-v9-dkmad                              4/4       Running   0          3m
kube-scheduler-kubernetes-master               1/1       Running   0          3m
kube-ui-v3-mt7nw                               1/1       Running   0          3m
l7-lb-controller-b56yf                         2/2       Running   0          3m
monitoring-influxdb-grafana-v2-lxufh           2/2       Running   0          3m

我在

config default.sh

中唯一更改的是从gcp到elasticsearch的KUBE_LOGGING_DESTINATION变量：

$ git diff cluster/gce/config-default.sh
diff --git a/cluster/gce/config-default.sh b/cluster/gce/config-default.sh
index fd31820..2e37ebc 100755
--- a/cluster/gce/config-default.sh
+++ b/cluster/gce/config-default.sh
@@ -58,7 +58,7 @@ ENABLE_CLUSTER_MONITORING="${KUBE_ENABLE_CLUSTER_MONITORING:-googleinfluxdb}"

 # Optional: Enable node logging.
 ENABLE_NODE_LOGGING="${KUBE_ENABLE_NODE_LOGGING:-true}"
-LOGGING_DESTINATION="${KUBE_LOGGING_DESTINATION:-gcp}" # options: elasticsearch, gcp
+LOGGING_DESTINATION="${KUBE_LOGGING_DESTINATION:-elasticsearch}" # options: elasticsearch, gcp

 # Optional: When set to true, Elasticsearch and Kibana will be setup as part of the cluster bring up.
 ENABLE_CLUSTER_LOGGING="${KUBE_ENABLE_CLUSTER_LOGGING:-true}"

---

我在本地虚拟机（Ubuntu14.04.3 LTS）上运行kubernetes群集，看起来我使用的是v1.0.6版本$sudo kubectl版本客户端版本：version.Info{Major:“1”，Minor:“0”，GitVersion:“v1.0.6”，GitCommit:“388061F00F00D9E4D641F9ED4971C775E1654579D”，GitRestate:“clean”}服务器版本：version.Info{Major:“1”，Minor:“0”，GitVersion:“v1.0.6”，GitCommit:“388061F00D9E4D641ED4971C775E1654579D”，GitRestate:“clean”}您按照哪些说明设置kubernetes？您修改了哪些文件？您链接到的说明谈到了修改

config default.sh

文件以创建GCE集群。Ubuntu的

config default.sh

文件默认为弹性搜索，但节点日志记录被禁用（）。@EricTune..我遵循了“Kubernetes在裸机Ubuntu节点上的部署”。我还做了KUBERNETES_PROVIDER=ubuntu./deployAddons.sh。请注意，我已经在两个节点上安装并运行了应用程序和参与者，并且没有问题。我能够手动启动elasticsearch和kibana，运行es controller.yaml，es service.yaml，kibana-controller.yaml，kubernetes/cluster/addons/fluentd elasticsearch下的kibana-service.yaml，但在kibana中配置索引模式时遇到问题。我得到的是“模式与任何现有索引都不匹配”…我可能缺少一些内容。更清晰的格式设置-用户没有使用代码块