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

[Cloud Security] Create upgrade agentless deployment background task #207143

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Omolola-Akinleye
Copy link
Contributor

Summary

Summarize your PR. If it involves visual changes include a screenshot or gif.
This PR add background task to upgrade Agentless Deployments after Kibana Stack has been upgrade in ESS. Once the Kibana stack upgrades,

  1. Fetch agentless policies with package policies that have agents
  2. Check if agentless agents version less than latest available upgrade version and current stack version in kibana
  3. Calls Agentless Upgrade Endpoint to upgrade agentless deployment.
  4. Agent should be upgraded to latest available upgraded version

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests were updated or added to match the most common scenarios
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

@Omolola-Akinleye Omolola-Akinleye added backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) v8.18.0 labels Jan 18, 2025
@Omolola-Akinleye Omolola-Akinleye self-assigned this Jan 18, 2025
@elasticmachine
Copy link
Contributor

🤖 Jobs for this PR can be triggered through checkboxes. 🚧

ℹ️ To trigger the CI, please tick the checkbox below 👇

  • Click to trigger kibana-pull-request for this PR!
  • Click to trigger kibana-deploy-project-from-pr for this PR!

@Omolola-Akinleye Omolola-Akinleye added the Team:Cloud Security Cloud Security team related label Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) Team:Cloud Security Cloud Security team related v8.18.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants