alerta
ca-issuer
calico
ceph-client
ceph-mon
ceph-osd
ceph-provisioners
ceph-rgw
daemonjob-controller
doc
source
requirements.txt
elastic-apm-server
elastic-filebeat
elastic-metricbeat
elastic-packetbeat
elasticsearch
etcd
falco
flannel
fluentbit
fluentd
gnocchi
grafana
helm-toolkit
ingress
kafka
kibana
kube-dns
kubernetes-keystone-webhook
kubernetes-node-problem-detector
ldap
libvirt
local-storage
lockdown
mariadb
memcached
metacontroller
mongodb
nagios
namespace-config
nfs-provisioner
openvswitch
playbooks
podsecuritypolicy
postgresql
powerdns
prometheus
prometheus-alertmanager
prometheus-blackbox-exporter
prometheus-kube-state-metrics
prometheus-node-exporter
prometheus-openstack-exporter
prometheus-process-exporter
rabbitmq
redis
registry
releasenotes
roles
tiller
tools
zookeeper
zuul.d
.gitignore
.gitreview
CONTRIBUTING.rst
Makefile
README.rst
setup.cfg
setup.py
tox.ini
yamllint-templates.conf
yamllint.conf

This chart could deploy fluentd either as a Deployment or a Daemonset. Both options would use the deployment-fluentd template with various sections toggled off based on values.yaml I'd like to know - Does anyone run this chart as a Deployment? We can simplify the chart, and zuul gates, by changing the chart to deploy a Daemonset specifically. Change-Id: Ie88ceadbf5113fc60e5bb0ddef09e18fe07a192c