Is init container still needed?

[rittneje]

According to the example yaml, we need to use an init container as a workaround for some issue in the fluentd image.

amazon-cloudwatch-container-insights/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/fluentd/fluentd.yaml

Lines 364 to 375 in 2ae134f

	# Because the image's entrypoint requires to write on /fluentd/etc but we mount configmap there which is read-only,
	# this initContainers workaround or other is needed.
	# See https://github.com/fluent/fluentd-kubernetes-daemonset/issues/90
	initContainers:
	- name: copy-fluentd-config
	image: busybox
	command: ['sh', '-c', 'cp /config-volume/..data/* /fluentd/etc']
	volumeMounts:
	- name: config-volume
	mountPath: /config-volume
	- name: fluentdconf
	mountPath: /fluentd/etc

However, we are not observing any problems without this init container, and based on this issue I think this may have been fixed long ago. fluent/fluentd-kubernetes-daemonset#161

Is this init container still needed? If not can it be removed from the example yaml?