Endpoint system requirements

[natasha-moore-elastic]

Resolves #4636. Adds Endpoint system requirements to ESS and serverless docs.

Previews:

• ESS: Elastic Endpoint requirements
• Serverless: Install Elastic Endpoint manually

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[elasticdocs]

🚀 Built co-preview-docs successfully!

• https://docs-elastic-bwb08rn5e-elastic-dev.vercel.app

• Built with commit 7f2f2a9

Issues? Visit #next-docs in Slack

[joepeeples]

It's not incorrect, but the table format used this way seems a little unexpected because it could only ever have one single row. I think rotating the table, so the left column has types of info and the right column has their values, is more typical, like this example.

[natasha-moore-elastic]

It's not incorrect, but the table format used this way seems a little unexpected because it could only ever have one single row. I think rotating the table, so the left column has types of info and the right column has their values, is more typical, like this example.

I agree, @joepeeples – I tried to do that initially, and it works for ESS docs, but we don't seem to support headerless tables in serverless docs (I tried both regular MD syntax and the DocTable component). I suppose we can add a header with something like Requirement | Value as column titles?

[natasha-moore-elastic]

@roxana-gheorghe, just to double-check, is there any information that we should add before the table (similar to what we have here)?

[joepeeples]

LGTM, thanks!