Promtail should not rely on Loki being enabled

Bug

private-registry is not created if promtail is enabled and loki is not. Recent commit actually did this on purpose however there is a need to be able to run promtail without loki in the same cluster. Fluentbit does not have this same dependency on Elasticsearch

Description

Enabled promtail without enabling loki and the private-registry secret was not created in the logging namespace.

This seems to have been a design choice:!1588 (merged)

And tested that this condition would work however if that private-registry does not exist before promtail is pulled from ironbank the pull will fail. I suspect the test showing promtail launched they had already cached the image.

BigBang Version

1.52

via the deployed umbrella git tag

kubectl get gitrepository -n bigbang