set Suppress_Type_Name to On for ElasticSearch output

[SlavikCA]

For ElasticSearch output, the default value of Suppress_Type_Name is Off:
https://docs.fluentbit.io/manual/pipeline/outputs/elasticsearch

That means, that out of the box FluentBit can only work with ElasticSearch version 6.x.
If output sent to ElasticSearch 8.x, the output will fail.

Support for Elastic 6.x was ended ~2 years ago.

Changing the value of Suppress_Type_Name to On will enable it to work with version 8.x out of the box.

[stevehipwell]

@SlavikCA do you use the output value without modification? IMHO they're just there as an example and shouldn't be used, a better pattern would be to switch the value to a stdout output so the chart can be deployed in a working state.

[SlavikCA]

@stevehipwell
I took that values.yaml file, modified it and used it.

better pattern would be to switch the value to a stdout output

Can you clarify? Are you saying that instead of ElasticSearch output, the better idea is to use stdout?

[stevehipwell]

@SlavikCA when you modified values.yaml did you change config.outputs? If so the values you're submitting here would just be overridden anyway.

AFAIK the current config.outputs value would only work for someone who had an ES cluster running in the same namespace with the hostname (service name) elasticsearch-master which makes it unsuitable for just bringing up an instance to test.

[SlavikCA]

I'm using ElasticSearch which is not hosted in the Kubernetes. It runs standalone.
So, yes, I updated config.outputs to point to my ES, username, password. But I based it on this example of values.yaml. And it didn't work with ES 8 because of Suppress_Type_Name.

So, this PR changes this example to make the example more modern - it will work for ES 8 now.

[stevehipwell]

@SlavikCA my issue here is that to make the change, which will almost certainly be overridden by all end users, requires a new chart release which will cause a significant amount of churn. So as to my second point, if we were making changes here I'd prefer to remove the ES config so it can't be incorrect and make a default installation work without needing to override this part.