Add ECK 2.16

[naemono]

This adds the ECK 2.16 branch to the build list. ECK 2.16.0 is planned for release on December 12th.

This has been delayed to Dec 19th.

[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.}

[naemono]

@elastic/docs-repo-owners Could anyone give this a review please? The linked buildkite build did pass after a retry.

[kilfoyle]

LGTM! 🚀

[naemono]

LGTM! 🚀

thank you for the review, but how do I get this merged since the docs build shows failed but actually succeeded?

[kilfoyle]

@naemono The docs-build-pr CI check log shows this error:

WARNING: invalid reference: release-notes-2.16.0

I'm confused as to why this fails though, because I do see that release-notes-2.16.0 file here in the cloud-on-k8s repo's 2.16 branch.

[naemono]

@naemono The docs-build-pr CI check log shows this error:

WARNING: invalid reference: release-notes-2.16.0

I'm confused as to why this fails though, because I do see that release-notes-2.16.0 file here in the cloud-on-k8s repo's 2.16 branch.

it wasn't originally in that Branch, and that was fixed yesterday so I think the logs you're looking at may be outdated

[kilfoyle]

@naemono Sorry, I missed that the docs build passed on the second run. I've just pushed an empty commit to this PR to relaunch everything, and hopefully that will be the magic we need. :-)