bdaf866a4e
This adds required changes to the Fluentd chart to allow for deploying Fluentd as either a deployment or a daemonset. This follows the pattern laid out by the ingress chart. This also updates the single and multinode jobs to deploy fluentd as both a daemonset and a deployment for validation Change-Id: I84353a2daa2ce56ff59882a8d33203286ed27e06 Signed-off-by: Steve Wilkerson <sw5822@att.com> |
||
---|---|---|
.. | ||
000-install-packages.sh | ||
001-setup-apparmor-profiles.sh | ||
005-deploy-k8s.sh | ||
010-deploy-docker-registry.sh | ||
020-ingress.sh | ||
030-nfs-provisioner.sh | ||
040-ldap.sh | ||
070-kube-state-metrics.sh | ||
080-node-exporter.sh | ||
090-process-exporter.sh | ||
150-falco.sh | ||
fluentbit.sh | ||
fluentd-daemonset.sh | ||
grafana-selenium.sh | ||
kibana-selenium.sh | ||
nagios-selenium.sh | ||
openstack-exporter.sh | ||
prometheus-selenium.sh | ||
wait-for-pods.sh |