-
Notifications
You must be signed in to change notification settings - Fork 159
Add limitations to CA rotation docs #2971
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔍 Preview links for changed docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM except you might consider using {{agent}} for "Elastic Agent" and {{beats}} for "Beats"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good from a docs perspective. It would still be good to get 👀 from the dev team since the discussion in the related issue is relatively old. Based on who was active in that thread... maybe @AndersonQ could take a look?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, sorry for the delay in looking at this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If memory does not betray me, it looks good :)
This PR updates the Rotate SSL/TLS CA certificates page with a new section ('Limitations') to clarify current product behaviors.
This addition addresses open questions raised in How to replace expired or soon to expire CA in Fleet (Elastic Agent & Fleet Server) and provides explicit documentation of known limitations.