[ECK 3.3] - AutoOps documentation.

[naemono]

Summary

Adds/Updates AutoOps ECK documentation for self-managed clusters on ECK for the upcoming 3.3 ECK release.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

Tool(s) and model(s) used:

• Cursor/Auto

[github-actions]

Vale Linting Results

Summary: 1 suggestion found

💡 Suggestions (1)

File	Line	Rule	Message
deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md	100	Elastic.Repetition	"Docker" is repeated.

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

🔍 Preview links for changed docs

• deploy-manage/deploy/cloud-on-k8s/autoops.md
• deploy-manage/deploy/cloud-on-k8s/configuration-autoops.md
• deploy-manage/deploy/cloud-on-k8s/logstash.md
• deploy-manage/deploy/cloud-on-k8s/managing-deployments-using-helm-chart.md
• deploy-manage/deploy/cloud-on-k8s/orchestrate-other-elastic-applications.md
• deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md

[wajihaparvez]

Hi @naemono
Thanks for making these updates to the docs! I'm just waiting on confirmation from the AutoOps team about a couple of things before I can review and approve on behalf of docs

[barkbay]

@naemono I just realized that this PR has been created against the main branch. Not sure if this is expected since it should only be merged when ECK 3.3 is released, which also requires other pages to be updated like https://github.com/elastic/docs-content/blob/main/deploy-manage/deploy/cloud-on-k8s.md#supported-versions-k8s-supported.

[naemono]

@naemono I just realized that this PR has been created against the main branch. Not sure if this is expected since it should only be merged when ECK 3.3 is released, which also requires other pages to be updated like https://github.com/elastic/docs-content/blob/main/deploy-manage/deploy/cloud-on-k8s.md#supported-versions-k8s-supported.

I wouldn't mind some clarification here. With the applies_to tags, I was thinking that when this is merged shouldn't matter quite as much, but I'm fine with just merging this post-release; I just wanted to bring it up as a discussion point. I spoke to @barkbay about this and will create a branch for 3.3, and just merge there until release, similar to what we do in the ECK repo.