Align elastic-agent-standalone manifest with the kubernetes package changes

[tetianakravchenko]

Signed-off-by: Tetiana Kravchenko [email protected]

What does this PR do?

In kubernetes package were added some data-streams configuration adjustments. This PR backports those changes to elastic-agent standalone manifest.

Why is it important?

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes Replace logfile input with filestream in elastic agent's standalone Kubernetes manifest #29565

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label. Could you fix it @tetianakravchenko? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-12-23T12:06:19.232+0000

• Duration: 58 min 39 sec

• Commit: 0040823

Test stats 🧪

Test	Results
Failed	0
Passed	3
Skipped	0
Total	3

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[MichaelKatsoulis]

I believe we should keep the manifest as simple as possible and leave the defaults with not comments. The extra fields are documented for anyone who wants to change settings. I would just leave

parsers:
        - container: ~

[tetianakravchenko]

it is current default - see https://github.com/elastic/integrations/blob/master/packages/kubernetes/data_stream/container_logs/agent/stream/stream.yml.hbs#L7-L10, was introduced in elastic/integrations#2345 to make it possible to configure those default values

[MichaelKatsoulis]

Defaults are all streams and auto format. See in https://github.com/elastic/integrations/blob/master/packages/kubernetes/data_stream/container_logs/manifest.yml#L27.
For filestream input if we don't set them like

- container: ~

it takes the defaults.
For additionalParsersConfig we just added the possibility for a user to add another parser via advanced options.
The default is still commented out.

[tetianakravchenko]

ah, ok, I understood what do you mean, I thought to set it the same way as done in the package, but you are right - in the end it is the same.
setting default values implicitly - 7c00ce9

[MichaelKatsoulis]

Was this change intentional ? This is a proposed manifest and I don't think elastic-package-stack_elasticsearch_1 is of any value to a customer.

[tetianakravchenko]

I've already removed it - it was used to test locally

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[ChrsMark]

Thanks for working on this! I left one small comment about the skip_older which is mostly to provide option for disabling this and hence we should better avoid exposing this with the default value.

[ChrsMark]

🚀