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> |
||
---|---|---|
.. | ||
apparmor | ||
armada | ||
common | ||
elastic-beats | ||
keystone-auth | ||
multinode | ||
network-policy | ||
openstack-support | ||
osh-infra-logging | ||
osh-infra-monitoring | ||
podsecuritypolicy | ||
tenant-ceph |