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

[Fleet] Upgrade and auto-upgrade of packages #72714

Open
ph opened this issue Jul 21, 2020 · 7 comments
Open

[Fleet] Upgrade and auto-upgrade of packages #72714

ph opened this issue Jul 21, 2020 · 7 comments
Assignees
Labels
design Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@ph
Copy link
Contributor

ph commented Jul 21, 2020

Summary of the problem

We are expecting the user to uses multiples integrations, integrations will have their own release schedule
and will not be tied to a specific stack release process. This cause a few problems:

  • How do I know that integration can be updated?
  • How do I know if my system is up to date?

User stories:

  • As a fleet administrator I should be able to see what integrations need to be upgraded.
  • As a fleet administrator I should be able to turn on background update of integrations.
  • As a fleet administrator I should know what integrations have been upgraded in the background.
  • As a fleet administrator I should know if any issues happened if some auto-upgraded failed.
  • As a fleet administrator I should know which Agent configuration can be updated to use the new version of the integration.

Other*

Upgrading an integration package doesn't mean that configuration is updated.

@ph ph added design Team:Fleet Team label for Observability Data Collection Fleet team labels Jul 21, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

@ph
Copy link
Contributor Author

ph commented Jul 21, 2020

cc @neptunian Can you take a look if there any others user stories we are missing?

@ph
Copy link
Contributor Author

ph commented Jul 21, 2020

maybe linked to the deployment ui #72537

@hbharding hbharding self-assigned this Jul 27, 2020
@mostlyjason
Copy link
Contributor

Related to #64253

@mostlyjason
Copy link
Contributor

@jonathan-buttner and @neptunian can you propose updates to the user stories above based on what we discussed?

@jonathan-buttner
Copy link
Contributor

One that I can think of is:
As a non-administrator I should be made aware that integrations are available for upgrade.

I think it could be useful for a non-admin user (a user that doesn't have the right privileges to install packages etc) to know that integrations are available for upgrade even though they might not be able to do the install. Maybe they could reach out to the admin to do the installation for them.

I'm not sure how to phrase the user store or if there really needs to be one, but I think there is value in users of the Security app being made aware that there is an upgrade available specifically for the endpoint integration.

@neptunian
Copy link
Contributor

It doesn't like we have a solution for auto upgrades yet, but assuming we find one, I don't think the user stories have changed and they seem to cover the correct cases. I do agree with @jonathan-buttner that it could be useful for any user to know an upgrade is available.

@jen-huang jen-huang changed the title Upgrade and auto-upgrade of integrations packages [Fleet] Upgrade and auto-upgrade of integrations packages Apr 27, 2021
@jen-huang jen-huang changed the title [Fleet] Upgrade and auto-upgrade of integrations packages [Fleet] Upgrade and auto-upgrade of packages Apr 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

7 participants