Charts: [stable/fluent-bit] No service created

[donkeyx]

Describe the bug
Error when installing fluent-bit chart which is looking for a service endpoint called "fluentd"

Version of Helm and Kubernetes:

helm version
Client: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-20T04:49:16Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.8", GitCommit:"4e209c9383fa00631d124c8adcc011d617339b3c", GitTreeState:"clean", BuildDate:"2019-02-28T18:40:05Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
stable/fluent-bit

What happened:
After deploying the chart, I noticed it was getting an error from the pods, looking for a service named "fluentd" which does not exist.

helm install --name fluentd-bit stable/fluent-bit --set=backend.es.host=elasticsearch-master --namespace logging

fluentd pod error logs :

[2019/07/04 01:13:18] [error] [out_fw] no upstream connections available
[2019/07/04 01:13:18] [ warn] net_tcp_fd_connect: getaddrinfo(host='fluentd'): Name or service not known
[2019/07/04 01:13:18] [error] [out_fw] no upstream connections available
[2019/07/04 01:13:19] [ warn] net_tcp_fd_connect: getaddrinfo(host='fluentd'): Name or service not known
[2019/07/04 01:13:19] [error] [out_fw] no upstream connections available

services in the logging namespace:

kubectl get svc --namespace logging
NAME                            TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
elasticsearch-master            ClusterIP   100.70.169.58    <none>        9200/TCP,9300/TCP   19h
elasticsearch-master-headless   ClusterIP   None             <none>        9200/TCP,9300/TCP   19h
kibana

status of the fluentd-bit helm service:

helm status fluentd-bit
LAST DEPLOYED: Thu Jul  4 12:01:51 2019
NAMESPACE: logging
STATUS: DEPLOYED

RESOURCES:
==> v1/Pod(related)
NAME                          READY  STATUS   RESTARTS  AGE
fluentd-bit-fluent-bit-4hn7d  1/1    Running  0         81m
fluentd-bit-fluent-bit-cclgm  1/1    Running  0         81m
fluentd-bit-fluent-bit-pdwmm  1/1    Running  0         81m

==> v1/Secret
NAME                                  TYPE    DATA  AGE
fluentd-bit-fluent-bit-es-tls-secret  Opaque  1     81m

==> v1/ConfigMap
NAME                           DATA  AGE
fluentd-bit-fluent-bit-config  6     81m
fluentd-bit-fluent-bit-test    2     81m

==> v1/ServiceAccount
NAME                    SECRETS  AGE
fluentd-bit-fluent-bit  1        81m

==> v1/ClusterRole
NAME                    AGE
fluentd-bit-fluent-bit  81m

==> v1/ClusterRoleBinding
NAME                    AGE
fluentd-bit-fluent-bit  81m

==> v1beta1/DaemonSet
NAME                    DESIRED  CURRENT  READY  UP-TO-DATE  AVAILABLE  NODE SELECTOR  AGE
fluentd-bit-fluent-bit  3        3        3      3           3          <none>         81m


NOTES:
fluent-bit is now running.

It will forward all container logs to the svc named fluentd on port: 24284

What you expected to happen:
I would have expected the chart to create all components needed for it to run, including the service that its looking for?

How to reproduce it (as minimally and precisely as possible):

Not sure what else to say in here but, all i have done is the install and passed the elastic service name and namespace. But there is no service called fluentd created.

helm install --name fluentd-bit stable/fluent-bit --set=backend.es.host=elasticsearch-master --namespace logging

Anything else we need to know:

[Towmeykaw]

The default backend type is forward which tries to forward the messages to fluentd.
Just include --set backend.type=es and it should work

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity.