control-service: Make fluentdconfig configurable

[gabrielgeorgiev1]

This change allows the fluentdconfig to be altered
through the Values.yml file. The purpose of this is
that making changes to a deployed version of
control-service no long requires pushing changes to
the main control-service repository.

Testing done:
With the following config in Values.yml:

fluentd:
  enabled: true
  filter: |-
    @type parser
    key_name log
    reserve_data true
    remove_key_name_field true
    <parse>
      @type json
    </parse>
  match: |-
    @type elastic

We get the following config:

apiVersion: logs.vdp.vmware.com/v1beta1
kind: FluentdConfig
metadata:
  name: pipelines-control-service-parser
spec:
  fluentconf: |
    <filter $labels(app_kubernetes_io/name=pipelines-control-service)>
      @type parser
      key_name log
      reserve_data true
      remove_key_name_field true
      <parse>
        @type json
      </parse>
    </filter>
    <match $labels(app_kubernetes_io/name=pipelines-control-service)>
      @type elastic
    </match>

If we extend the config the with a fluentd.extra value:

  extra: |-
    <source>
      @type http
      port 8090
    </source>
    <system>
      some system config
    </system>

We get the following fluentdconfig:

apiVersion: logs.vdp.vmware.com/v1beta1
kind: FluentdConfig
metadata:
  name: pipelines-control-service-parser
spec:
  fluentconf: |
    <source>
      @type http
      port 8090
    </source>
    <system>
      some system config
    </system>
    <filter $labels(app_kubernetes_io/name=pipelines-control-service)>
      @type parser
      key_name log
      reserve_data true
      remove_key_name_field true
      <parse>
        @type json
      </parse>
    </filter>
    <match $labels(app_kubernetes_io/name=pipelines-control-service)>
      @type elastic
    </match>

Signed-off-by: gageorgiev [email protected]

[antoniivanov]

Please avoid said in testing done "local", "manual", those do not really tell anything to the reader.

Reminder from the git template
In case there is any manual tests needed describe the exact steps -
what were the commands, what was the output, what was expected, details of your testing environment.

[antoniivanov]

Everything looks good to me. I want to review how it was tested only. How we are sure the produced config is valid and working.

[antoniivanov]

Thanks. Looks good to me.