Skip to content
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

Add known issue for Fleet setup > 1000 policies #825

Merged
merged 2 commits into from
Jan 18, 2024

Conversation

kilfoyle
Copy link
Contributor

This updates the 8.12.0 Release Notes with a Fleet setup known issue, as requested here.

Josh, Kyle, let me know if I've misunderstood the issue.

Screenshot 2024-01-18 at 9 54 32 AM

@kilfoyle kilfoyle requested a review from a team as a code owner January 18, 2024 14:57
Copy link

A documentation preview will be available soon.

Help us out by validating the Buildkite preview and reporting issues here.
Please also be sure to double check all images to ensure they are correct in the preview.

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.

Copy link

mergify bot commented Jan 18, 2024

This pull request does not have a backport label. Could you fix it @kilfoyle? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-/d./d is the label to automatically backport to the /d./d branch. /d is the digit
    NOTE: backport-skip has been added to this pull request.

Copy link
Member

@kpollich kpollich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding this!

@gergoabraham
Copy link

@kilfoyle thank you for the documentation! 🙇

I'd like to suggest to change the number: actually it can happen above 500 agent policies (512 precisely)

Copy link
Contributor

@karenzone karenzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kilfoyle kilfoyle merged commit c4f8067 into elastic:main Jan 18, 2024
5 checks passed
mergify bot pushed a commit that referenced this pull request Jan 18, 2024
* Add known issue for Fleet setup > 1000 policies

* Add 8.12 known issue for Fleet setup with >1000 policies

(cherry picked from commit c4f8067)
kilfoyle added a commit that referenced this pull request Jan 18, 2024
* Add known issue for Fleet setup > 1000 policies

* Add 8.12 known issue for Fleet setup with >1000 policies

(cherry picked from commit c4f8067)

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants