Fluentd Pods fail to deploy with Error/CrashLoopBack when using http:// in insecure LogForwarding Instance

Issue

• When defining the LogForwarding instance per Forwarding cluster logs using Log Forwarding, if you include "http://" in the endpoint for an insecure forwarder, it will incorrectly set the /etc/fluent/fluent.conf port and host on all fluentd pods, and they will fail to deploy with Error/CrashLoopBack.