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.

Sign up for GitHub

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

Jump to bottom

Update cloud_security_posture deployment instructions #3252

Closed
2 tasks
eyalkraft opened this issue May 2, 2022 · 1 comment
Closed
2 tasks

Update cloud_security_posture deployment instructions #3252

eyalkraft opened this issue May 2, 2022 · 1 comment
Labels
Team:Cloud Security Label for the Cloud Security team [elastic/cloud-security-posture]

Comments

@eyalkraft
Copy link
Contributor

eyalkraft commented May 2, 2022 •
edited
Loading

Motivation

Following the update of the agent k8s deployment Yamls (elastic/elastic-agent#381), the cloud_security_posture integration package README should be updated to include exact instructions for how to use the integration with agents that were deployed prior to this change to the manifest yaml files.

Additionally, since cloudbeat is released at 8.3, agents with version prior to it wouldn't be able to run it (? - make sure)

Definition of done

  • update the cloud_security_posture integration package README file
  • update the readme to indicate that the minimum agent version is X
@eyalkraft eyalkraft added the Team:Cloud Security Label for the Cloud Security team [elastic/cloud-security-posture] label May 2, 2022
@oren-zohar oren-zohar mentioned this issue May 11, 2022
Closed
@eyalkraft
Copy link
Contributor Author

Closing this duplicate after the issue was transferred:

@eyalkraft eyalkraft mentioned this issue May 15, 2022
Closed
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Team:Cloud Security Label for the Cloud Security team [elastic/cloud-security-posture]
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@eyalkraft @oren-zohar