Add docs for AutoOps on ECK#4792
Merged
wajihaparvez merged 16 commits intoelastic:mainfrom Feb 2, 2026
Merged
Conversation
Contributor
Vale Linting ResultsSummary: 23 suggestions found 💡 Suggestions (23)
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. |
Contributor
wajihaparvez
changed the title
arnonst
approved these changes
Jan 28, 2026
arnonst
left a comment
arnonst
left a comment
There was a problem hiding this comment.
LGTM!
@naemono - Can you review the page deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md
kilfoyle
reviewed
Jan 28, 2026
kilfoyle
reviewed
Jan 28, 2026
kilfoyle
reviewed
Jan 28, 2026
kilfoyle
reviewed
Jan 28, 2026
kilfoyle
reviewed
Jan 28, 2026
kilfoyle
reviewed
Jan 28, 2026
kilfoyle
reviewed
Jan 28, 2026
kilfoyle
reviewed
Jan 28, 2026
kilfoyle
approved these changes
Jan 28, 2026
Contributor
kilfoyle
left a comment
kilfoyle
left a comment
There was a problem hiding this comment.
LGTM! 🦖
This is very nicely organized! I added just a few super minor suggestions.
2 tasks
naemono
reviewed
Jan 28, 2026
Member
shainaraskas
left a comment
shainaraskas
left a comment
There was a problem hiding this comment.
some comments around the recurring self-managed problem and ECK availability
this thread about the self-managed terminology represents our strategy: https://elastic.slack.com/archives/C07APH4RCDT/p1769519793259699
naemono
reviewed
Jan 29, 2026
Contributor
naemono
left a comment
naemono
left a comment
There was a problem hiding this comment.
Couple more minor things I've seen.
Member
|
7.17 went EOL on Jan 15 so we should remove 7.17 from here 
|
shainaraskas
approved these changes
Jan 30, 2026
Member
shainaraskas
left a comment
shainaraskas
left a comment
There was a problem hiding this comment.
sorry about the full nightmare that this caused in the FAQ. this is an interesting use case, and the best reason I've seen in the past year to have some concept of a "not Elastic-managed" term. I will try to think about this more to make this problem less painful.
Changes look good/consistent. Couple of somewhat unrelated comments to consider but all good from the deployments terminology / versioning perspective now :)
Contributor
Author
|
@shainaraskas Some 7.1.7 customers are eligible to use AutoOps until 2027, but I agree that this is confusing. It's on my list to figure out with the PMs |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR:
Closes https://github.com/elastic/docs-content-internal/issues/499.
Generative AI disclosure