-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Cloud Security] Default CSPM integration to use Agentless as the setup technology. #205965
[Cloud Security] Default CSPM integration to use Agentless as the setup technology. #205965
Conversation
5f73293
to
5adad08
Compare
fe67912
to
d449e9a
Compare
...ections/agent_policy/create_package_policy_page/single_page_layout/hooks/setup_technology.ts
Show resolved
Hide resolved
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
...ections/agent_policy/create_package_policy_page/single_page_layout/hooks/setup_technology.ts
Outdated
Show resolved
Hide resolved
Pinging @elastic/fleet (Team:Fleet) |
...ections/agent_policy/create_package_policy_page/single_page_layout/hooks/setup_technology.ts
Show resolved
Hide resolved
...ications/fleet/sections/agent_policy/create_package_policy_page/single_page_layout/index.tsx
Outdated
Show resolved
Hide resolved
...ections/agent_policy/create_package_policy_page/single_page_layout/hooks/setup_technology.ts
Outdated
Show resolved
Hide resolved
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.
Looks Awesome! Just few suggestions and comments to understand if there side effects.
...ections/agent_policy/create_package_policy_page/single_page_layout/hooks/setup_technology.ts
Outdated
Show resolved
Hide resolved
After testing the PR in Build's security deployment, the default option is still Agent-based. |
...ections/agent_policy/create_package_policy_page/single_page_layout/hooks/setup_technology.ts
Outdated
Show resolved
Hide resolved
@Omolola-Akinleye, it is intentionally still defaulting to agent-based. This PR is in preparation for the changes and can be merged today. When we merge the following we will have agentless as the default selected option
I could have easily set the default selected value in the CSPM Fleet extension code, however, I would like us not to drift too far from the Fleet platform so that when the time comes to use the Fleet UI we will not be in a "super bad spot". |
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
LGTM! Okay got it sorry for the confusion |
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
Page load bundle
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
cc @seanrathier |
Starting backport for target branches: 8.x |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…up technology. (elastic#205965) (cherry picked from commit c30212f) # Conflicts: # x-pack/platform/plugins/shared/fleet/public/applications/fleet/sections/agent_policy/create_package_policy_page/single_page_layout/hooks/setup_technology.ts
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…up technology. (elastic#205965) (cherry picked from commit c30212f) # Conflicts: # x-pack/platform/plugins/shared/fleet/public/applications/fleet/sections/agent_policy/create_package_policy_page/single_page_layout/hooks/setup_technology.ts
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
1 similar comment
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…up technology. (elastic#205965) (cherry picked from commit c30212f) # Conflicts: # x-pack/platform/plugins/shared/fleet/public/applications/fleet/sections/agent_policy/create_package_policy_page/single_page_layout/hooks/setup_technology.ts
Friendly reminder: Looks like this PR hasn’t been backported yet. |
…up technology. (elastic#205965) (cherry picked from commit c30212f) # Conflicts: # x-pack/platform/plugins/shared/fleet/public/applications/fleet/sections/agent_policy/create_package_policy_page/single_page_layout/hooks/setup_technology.ts
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
…he setup technology. (#205965) (#206985) # Backport This will backport the following commits from `main` to `8.x`: - [[Cloud Security] Default CSPM integration to use Agentless as the setup technology. (#205965)](#205965) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"seanrathier","email":"sean.rathier@gmail.com"},"sourceCommit":{"committedDate":"2025-01-15T17:07:02Z","message":"[Cloud Security] Default CSPM integration to use Agentless as the setup technology. (#205965)","sha":"c30212f9c0d091bd2564592ac21a6ef2f30368c8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","Team:Cloud Security","backport:prev-minor","ci:project-deploy-security"],"title":"[Cloud Security] Default CSPM integration to use Agentless as the setup technology.","number":205965,"url":"https://github.com/elastic/kibana/pull/205965","mergeCommit":{"message":"[Cloud Security] Default CSPM integration to use Agentless as the setup technology. (#205965)","sha":"c30212f9c0d091bd2564592ac21a6ef2f30368c8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205965","number":205965,"mergeCommit":{"message":"[Cloud Security] Default CSPM integration to use Agentless as the setup technology. (#205965)","sha":"c30212f9c0d091bd2564592ac21a6ef2f30368c8"}}]}] BACKPORT-->
Summary
This PR prepares Fleet to default the agent deployment option to Agentless.
Key Changes:
setup_technology
hook more efficient by removing redundant agentless policy state change requests in thehandleSetupTechnologyChange
event.useEffect
in thesetup_technology
hook, reducing the number of re-renders for the page.These changes allow the agentless integration to default to Agentless deployment and improve the performance of the Fleet setup.
Depends on elastic/package-spec#850
Depends on elastic/package-registry#1263
Closes
Checklist
Reviewers should verify this PR satisfies this list as well.
release_note:*
label is applied per the guidelines