Using the repo version of elastic products has proven to be a no go.
For the very simple reason that if you use the method of update repo list and then upgrade packages you will be offline until you perform remediation.
For a few years now I have tried to make this work. It simply does not. Each release brings something new to the table and something else needs a little more hands on attention.
Example for deb:
Prompt> apt-get update
Prompt> apt-get upgrade
Instantly broken env. You are dropping events the second this happens. This should NEVER be the case. Lost events means lost trust in monitoring of target ENV's.
First we have the repos with out of date certs. Secondly a package update does NOT update internal configuration of DB or addons. Which results in LOST EVENTS. These are very simple problems but are consistently neglected with every single release.
I would like to propose a program of work that actually does make this work. I do love Elastic, But this upgrade patch path is unbelievably fragile. This needs to be a priority 1 type feature for upcomgin releases.